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

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

Maintenance Schedule

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