Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Planning Council/September 4 2013"
(→Progress on Action Items) |
(→Kepler Retrospective) |
||
Line 171: | Line 171: | ||
== Kepler Retrospective == | == Kepler Retrospective == | ||
− | * | + | * "what worked" |
− | + | ||
+ | * "what didn't work": | ||
== Next Meeting == | == Next Meeting == |
Revision as of 10:08, 4 September 2013
Contents
Logistics
Meeting Title: | Planning Council Conference Call |
Date & Time: | Wednesday, September 4, 2013, at 1200 Noon Eastern |
Dial in: | (See Asterisk service for complete details on SIP, potential new numbers, phone mute commands, etc.)
Phone Numbers: (Check Asterisk/Numbers for more or current phone numbers.)
|
Members and Attendees
|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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
- ?
Kepler SR1
- Two (known, approved) exceptions to "new features in SR1: Linux Tools, Stardust
Luna Planning
- Do we have agreement on the Luna Milestone/Release schedule: Luna/Simultaneous_Release_Plan#Schedule
- Topics for possible discussion:
- Who should we scold the most for not communicating well? :)
- Change policy on disabling all in M1 to require "actively joining"?
- See Wayne's proposal on new method: http://dev.eclipse.org/mhonarc/lists/eclipse.org-planning-council/msg02190.html
- Key aspects:
- Note to cross-project
- Planning Council (or, Wayne) enters their "entry" and +n date in database
- Deadline? M4 seems "late" for those already in? We've said "once in, always in". Hence, how does this interact with "disabling in aggregation"?
- Key aspects:
- See Wayne's proposal on new method: http://dev.eclipse.org/mhonarc/lists/eclipse.org-planning-council/msg02190.html
- Should "we" say anything about Java 5 vs. Java 6? (Have we already?)
- Should we revisit the policy about "release one month prior to SR"?
- How can (or should) we better capture what new features are in an SR for adopters awareness?
Progress on Action Items
- Editing of "Requirements Document"? (Dani and Neil)
- GSoC project for "Development Channel"? (Wayne)
- Improved "aggregator examples/doc". (dw -- no progress).
- [Orbit plan "by end of August". (dw -- no progress -- will likely be late, still "in September")]
Kepler Retrospective
- "what worked"
- "what didn't work":
Next Meeting
- October 2, 2013 - Regular First Wednesday Meeting
Reference
- EclipseCon face-to-face follow-through action items. For original meeting notes, see Planning_Council/March_24_2013 and for discussion leading to action items, see Planning_Council/April_10_2013. For last status update, see Planning_Council/May_8_2013.