Difference between revisions of "Planning Council/October 6 2010"

From Eclipsepedia

Jump to: navigation, search
(Helios SR1)
(Helios SR1)
Line 141: Line 141:
 
* 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.  
+
* One issue to document as feedback (that I have heard about from TPTP PMC/Planning Council Rep): 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?] 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 all teams involved ... 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. I also suggested the TPTP team communicate more directly with EMF team either through their mailing list or cross-project list, to let them know when impacted, but I think in this case, by the time it was discovered there wasn't much to do. Anything we, as Planning Council, can do to help situations like this? Foster timely communication?
 +
 
 +
* The build machine failure and slow recovery was nearly enough to derail the scheduled release. Not sure what more we can do, but glad to hear IT team will provide more support for build machine recovery (See {{bug|325969}}.
  
 
=== Maintenance Schedule ===
 
=== Maintenance Schedule ===

Revision as of 10:43, 6 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

Chris Aniszczyk Technology (PMC)
John Arthorne [and Paul Webster] Eclipse (PMC)
Oliver Cole Tptp (PMC) X
Brian Payton Datatools (PMC)
Anthony Hunter Tools (PMC)
Oisin Hurley Stp (PMC)
Ed Merks Modeling (PMC)
Thomas Watson Rt (PMC)
David Williams WTP (PMC) (appointed Chair)
Gary Xue Birt (PMC)

Strategic Reps

Cedric Brun OBEO (Strategic Developer)
Stefan Daume Cloudsmith Inc.(Strategic Developer)
Neil Hauge Oracle (Strategic Developer)
Kaloyan Raev SAP AG (Strategic Developer)
Markus Knauer Innoopract (Strategic Developer)
Christian Kurzke Motorola (Strategic Developer)

Appointed

Wayne Beaton Eclipse Foundation (appointed)


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
X = not expected

Inactive

 ? Nokia (Strategic Developer) X
 ? CA Inc. (Strategic Consumer) X
 ? brox IT-Solutions GmbH (Strategic Developer) X


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



Announcements

  •  ?

Helios SR1

  • Any issues? complaints?
  • One issue to document as feedback (that I have heard about from TPTP PMC/Planning Council Rep): 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?] 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 all teams involved ... 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. I also suggested the TPTP team communicate more directly with EMF team either through their mailing list or cross-project list, to let them know when impacted, but I think in this case, by the time it was discovered there wasn't much to do. Anything we, as Planning Council, can do to help situations like this? Foster timely communication?
  • The build machine failure and slow recovery was nearly enough to derail the scheduled release. Not sure what more we can do, but glad to hear IT team will provide more support for build machine recovery (See bug 325969.

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

Indigo Requirements

Tracking "setup" required from Foundation in bug 321522

See initial Indigo Wiki page

Issues and Proposal for 3.7 versus 4.1

Other business

  •  ?

ToDo Items

  •  ?

Next Meeting

November 3, 12 noon Eastern

Reference

Indigo Simultaneous Release

Planning Council Members

Simultaneous Release Roles and Simultaneous Release Roles/EMO