Planning Council/December 07 2011

Logistics

Meeting Title:	Planning Council Conference Call
Date & Time:	Wednesday, December 07, 2011, at 1200 Eastern
Dial-in:	For the call-in numbers, see the "Project Review" number on Foundation Portal page.

Members and Attendees

PMC (and Strategic) Reps Chris Aniszczyk Technology (PMC) John Arthorne Eclipse (PMC) Mik Kersten Mylyn (ALM) PMC Brian Payton Datatools (PMC) Doug Schaefer Tools (PMC) Adrian Mos SOA (PMC) Ed Merks Modeling (PMC) Jesse McConnell Rt (PMC) David Williams WTP (PMC) (appointed Chair) Gary Xue Birt (PMC) Wayne Beaton Eclipse Foundation (appointed)

Strategic Reps Cedric Brun OBEO (Strategic Developer) Stefan Daume Cloudsmith Inc.(Strategic Developer) Neil Hauge Oracle (Strategic Developer) Kaloyan Raev SAP AG (Strategic Developer) Pascal Rapicault Sonatype (Strategic Developer) Markus Knauer Innoopract (Strategic Developer) Christian Kurzke Motorola (Strategic Developer) Achim Loerke BREDEX (Strategic Developer) (PMC rep) Actuate (Strategic Developer) X (PMC rep) IBM (Strategic Developer) X

Inactive [no name] TPTP (PMC) X [no name] CA Inc. (Strategic Consumer) X

Note: "Inactive" refers to Strategic Members or PMCs we have not heard from for a while, and have been unable to convince to participate. Those members can become active again at any time. Contact David Williams if questions.

Note: feel free to correct any errors/omissions in above attendance record.
Y = Yes, attended
N = No, did not
R = regrets sent ahead of time
D = delegated
X = not expected

Announcements

• Any?

Indigo SR2

• Anything?

Juno Plan and Requirements

M4

• Any issues? Everyone in? Any exceptions known?

Requirements

Review Requirements for substance and wording. See last meeting notes from November 23, 2011 for notes of previous discussion.

The things to focus on, for this meeting, are

• the proposed changes for Juno Release

• in particular, the new requirement: Documenting compliance

• and, since last meeting was not well attended, we will confirm, again, everyone supports the new requirement asking to make it easy to get released source.

Other clarifications?

• Other comments/improvements to plan?

Checklist (aka tracker)

From last meeting, concluded there was not resources to support information on Portal, but we'd add section asking for "statement" in review documentation, as I've written up in the new requirement: Documenting compliance. Need to "disconnect" portal dialogs, tracked in bug 364647.

From last meeting, Longer term, not in time for Juno, fields such as link to rampdown plan, link to accessibility testing, link to API policy, retention policy, etc. will be part of the new "super portal" for projects to fill in, or not, depending on type of release, needs of the project, etc.

Other business

• Name that release. Juno+1. Need volunteer to drive community discussion and vote.

• Anything else?

Next Meeting

• January 4, 2012 (our regular "first Wednesday" meeting, at Noon Eastern).

Reference

Juno Wiki page

Planning Council/Indigo retrospective

Planning Council Members

Simultaneous Release Roles and Simultaneous Release Roles/EMO