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/October 6 2010"
(→Indigo Plan and Schedule) |
(→Helios SR1) |
||
| Line 140: | Line 140: | ||
* Any issues? complaints? | * Any issues? complaints? | ||
| + | |||
| + | One issue to document, as feedback (that I have heard about): EMF didn't deliver any maintenance until the day after RC4 +1 day (but, unclear to me is if that was just download zips or any form of delivered fixes, even in helios repo?) ... but, I think, it deserves repeating that communication is key. We all need to make an effort to keep others informed. The late (or last minute?) changes caused TPTP to have to do a lot of re-work and was made worse by there being no notice or announcement on cross-project list. I'm sure there's many things that could have been different, from many teams .. but just documenting this case as once example of the importance of keeping others informed. Not to mention, of course, that incremental delivery of fixes allows for better testing. | ||
=== Maintenance Schedule === | === Maintenance Schedule === | ||
Revision as of 17:45, 5 October 2010
Contents
Logistics
| Meeting Title: | Planning Council Conference Call |
| Date & Time: | Wednesday, October 6, 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
|
Announcements
- ?
Helios SR1
- Any issues? complaints?
One issue to document, as feedback (that I have heard about): EMF didn't deliver any maintenance until the day after RC4 +1 day (but, unclear to me is if that was just download zips or any form of delivered fixes, even in helios repo?) ... but, I think, it deserves repeating that communication is key. We all need to make an effort to keep others informed. The late (or last minute?) changes caused TPTP to have to do a lot of re-work and was made worse by there being no notice or announcement on cross-project list. I'm sure there's many things that could have been different, from many teams .. but just documenting this case as once example of the importance of keeping others informed. Not to mention, of course, that incremental delivery of fixes allows for better testing.
Maintenance Schedule
SR2 Fourth Friday of February 2/25/2011
For detailed RC schedules, see Service Release Schedule in master plan
Helios Retrospective
Any additions?
Planning_Council/Helios_retrospective
Indigo Status
- M2 repo successfully created
- No M2 EPP packages
- And I've pestered Markus enough he's stopped returning my emails? :(
- 3 projects not in M2:
- jetty
- riena
- subversive
- Do they really intend to drop out? Or does this violate "once in always in"?
Indigo Plan and Schedule
Tracking "setup" required from Foundation in bug 321522
See initial Indigo Wiki page
Issues and Proposal for 3.7 versus 4.1
- See working notes in http://wiki.eclipse.org/Indigo/HowToAddress37And41Platform
Other business
- ?
ToDo Items
- ?
Next Meeting
November 3, 12 noon Eastern
Reference
Simultaneous Release Roles and Simultaneous Release Roles/EMO