Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Planning Council/June 02 2010"
(→Attendees) |
(→Next Year's Name) |
||
Line 146: | Line 146: | ||
Indigo it is | Indigo it is | ||
+ | |||
+ | === Who will lead the Planning Council next year? === | ||
+ | |||
+ | And the winner is ... | ||
=== Helios Release === | === Helios Release === |
Revision as of 15:53, 1 June 2010
Contents
Logistics
Meeting Title: | Planning Council Conference Call |
Date & Time: | Wednesday, June 02, 2010, at 1600 UTC / 1200 Eastern |
Dial-in: | For the call-in numbers, see the "Project Review" number on Foundation Portal page. |
Attendees
PMC (and Strategic) Reps
Strategic Reps
Appointed
|
Inactive
|
Helios
Next Year's Name
Should we do over? (Just kidding)
Indigo it is
Who will lead the Planning Council next year?
And the winner is ...
Helios Release
- Post RC4 exception process?
- Question from John:
According to our schedule there is one more week of potential builds after RC4, labeled "Helios Final". I see on the planning wiki that it says, "only emergency fixes for very serious regressions will be considered." I can't remember if we discussed this in the past, but what exactly does that mean? Does it mean the release train exception process should be used, with changes announced in advance and require approval from others? Or, will this be left to the discretion of each project? Unless we've already covered this, we should probably decide on that soon. Note, the Eclipse TLP doesn't plan on any contributions after RC4 at the moment, but I just want to know the process in advance in case something comes up...
- Any to kick off the train?
- Any gold stars to hand out?
Maintenance Schedule
Fourth Friday of September? 9/24/2010
Fourth Friday of February? 2/25/2011
Next Year's Schedule
Not ready to discuss details, but the problems with +1, +2, +3 category (and short times) should be well discussed.
Similarly, Oliver brought up issue with need for better "warm-up" rhythm, especially if a prereq project is late. (EMF's "last minute" M6 delivery added pressure to TPTP's ability to build/test in time). No specific actions, process or remedies are known, but ... maybe a reminder to cross-project list that intermediate or warm-up builds are good (especially if going to be near deadline).
Cross-Project Teams
Aggregation
Planning Council/Cross Project Teams/Aggregation
Other business
ToDo Items
Next Meeting
- June 2, Wednesday, Noon Eastern Time.
Reference
Simultaneous Release Roles and Simultaneous Release Roles/EMO