Jump to: navigation, search

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

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

Chris Aniszczyk Technology (PMC)
John Arthorne Eclipse (PMC)
Oliver Cole Tptp (PMC)
Brian Payton Datatools (PMC) R
Doug Gaff ??? Dsdp (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) R
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

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.



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...


Let's review compliance:
Top Level
Flat view
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

Helios Simultaneous Release

Planning Council Members

Simultaneous Release Roles and Simultaneous Release Roles/EMO