Helios/Simultaneous Release Plan
This page is under development. It is expected to be complete around Mid September.
- 1 Project Plan
- 2 Requirements For Participation
- 3 Milestones and Release Candidates
- 4 Communication
- 5 Helios Builds and P2 repository
- 6 Coordinated Service Releases
- 7 Projects
A roll up project plan for projects participating in the Helios simultaneous release is found here: http://www.eclipse.org/projects/project-plan.php?projectid=helios
Requirements For Participation
Projects that are part of Helios agree to abide by the requirements of the Eclipse Yearly Release.
[TBD: link to report]
Milestones and Release Candidates
The milestone dates are at roughly 6 week intervals. Any end-of-cycle release-candidate (RC) dates are typically one week apart. Each project has their deliveries due at times offset from the end-date, so that the project dependencies can come together in a reasonable order. These delivery times are based on the dependencies between projects -- they are called the +0, +1, +2, and +3 dependencies. Projects themselves decide if they are +0, +1, +2, or +3. The actual time-offset represented by these intervals change over the course of the year of development, being several days at first, but then only one day near the end of the release. The following calendar is the official schedule of the overall Helios Release. Projects are free to have their own schedules as long as they meet the Helios deliverables.
Note that projects choose their +n category based on major or primary dependencies. There are many cases a project might have to deliver pieces of their code a little earlier, if some project depends on it. These sorts of deviations are left the the projects to work out among themselves.
TODO: final "target" to be called "GA", not RC5.
Cross-Project Milestone & RC Status Reporting
Only negative status needs to be reported. It is essential for many aspect of the simultaneous release that communication be prompt and clear, on many topics. One of the most important ones, is if someone is not meeting some date or delivery. Put another way, we assume everyone is on target and has delivered their stuff unless a note is sent to cross-project list that you are delayed. Its better to be up front about it, so everyone knows what to expect, rather than to hope things turn out ok at the very last minute, since if you "miss" without saying anything you are more likely to impact other people, and miss your chance to be part of the release.
Mailing Lists and Newsgroups
Eclipse projects have three communication channels: a mailing list for developers, a newsgroup for users, and Bugzilla. While Helios is not a "project" per se, it will use the same structure:
Developer mailing list
- cross-projects-issues-dev - mailing list for developers and releng (see archives). This is the list to use to discuss build issues, announce changes in plans, slippage in deliverables, etc.
Users news group
If any doubt about where a bug belongs, it can always start in the "Cross-Project" component. (Under Eclipse Foundation > Community). If it really is a single-project's responsibility, it can be moved to that project. If it is a true cross-project bug, where several projects need to act, then it can stay in the cross-project component.
The Planning Council Mailing List
Because there has been confusion in the past, we'll be explicit here that the planning council mailing list (eclipse.org-planning-council) if for Planning Council business, not the Helios Release activities per se. While they sometimes overlap, there is no need to cross post. While anyone can request a subscription to the planning council list (for openness and transparency) the expectation is that only Planning Council members post to it.
But there are no planned calls for the release, per se, or for larger audiences, but they can be arranged if required or desired (for example, if needed for build coordination).
Helios Builds and P2 repository
[TBD: this section needs work still. Some is inaccurate or out of date]
A number of utilities have been written to automate the assembly of Callisto '06, Europa '07, Ganymede '08 and now Helios '09 builds. These are available in their own CVS respository. You can find more information about how this is organized and individual project responsibilities for the build on this Helios Build page (with old information on the Ganymede Build and Europa Build pages).
And with Helios we are using the Buckminster Helios Builder.
The Contributing to Helios Build page is where you go to learn how to add your project to the Helios build.
To obtain the latest published bits from Helios, use this URL:
It contains the latest milestone, release candidate, eventually the release itself, and then eventually service releases.
To obtain the latest working version, as we build up to a milestone or release, you can test the site at
Coordinated Service Releases
GA: 9/25/09 (last Friday of September)
In the SR1 rampdown, as shown in the following table, there will be 4 RCs, each spanning one week, with projects staging themselves into the build just one day apart.
Projects may elect not to participate in a particular RC, but have an obligation to fix any build problems that is related to their code or p2 repository.
RC1 will be in the middle of August, several weeks earlier than previous years, just to make sure we can still build, etc. Subsequent RCs dates are similar to previous years, except a "quiet" final week is also planned. (It is normally pretty quiet anyway ... this just formalizes it).
The Final week before GA will not have any further builds or contributions, but instead be reserved for final adopter testing and preparation and only emergency fixes for very serious regressions will be considered.
The 'promote' day (9/24) will be the day projects put final zips in their final spot (without displaying them) so they can propagate through the mirroring system. Similar for the p2 repository -- it will be replaced on 9/24 with the new content so it can start mirroring. Note: there is no plan to retain multiple versions in the common discovery repository (unless someone volunteers to do what's required to make that happen). At noon on 9/25 projects can make their final maintenance releases visible.
| EPP |
|Helios SR1 ("GA")||promote: 9/24||GA: 9/25|
2/26/10 (last Friday of February)
Rampdown similar to SR1.
| EPP |
|Helios SR2 ("GA")||promote: 2/25||GA: 2/26|
The projects that plan to participate in the Helios Simultaneous Release are listed below, along with their milestone offsets, leaders, release engineer, and ramp down policy.
|Project/Component||Project/Component Lead(s)||Release Engineer||Offset|
|Chieko Asakawa||Kentarou Fukuda||+3|
|Wenfeng Li||Xiaoying Gu||+2|
|Thomas Hallgren, Henrik Lindberg||Thomas Hallgren||+2|
|Doug Schaefer||Vivian Kong||+1|
|Andrey Platov||Andrey Platov||+3|
|Martin Oberhuber||Martin Oberhuber||+1|
|Eric Cloninger, Fabio Fantato||Fabio Fantato||+0|
|Gustavo de Paula||Diego Madruga Sandin||+1|
|Brian Fitzpatrick||Xiaoying Gu||+1|
|Scott Lewis||Ted Kubaska/Scott Lewis||+2|
|Peter Krogh, Doug Clarke||Peter Krogh||+1|
|Mike Wilson|| Kim Moir
|Thomas Watson, Jeff McAffer|| Kim Moir
| Ed Merks
| Ed Merks
| Markus Knauer
|Anthony Hunter||Anthony Hunter||+1|
|Richard Gronback||Richard Gronback||+2|
| Jean Bezivin
|Marc Dutoo, Florian Lautenbacher||Christian Saad||+3|
|Andreas Buchen||Erwin Margewitsch||+3|
| Kenn Hussey
| Frédéric Jouault
| Paul Elder
|Mik Kersten||Steffen Pingel||+3|
|Roy Ganor|| Roy Ganor
|Jochen Krause, Ruediger Herrmann||Ralf Sternberg, Ruediger Herrmann||+2|
|Christian Campo||Christian Campo||+3|
| Oisin Hurley
|| Oisin Hurley
|Igor Vinnykov||Igor Burilo||+2|
|Zsolt Beothy-Elo, Oliver Wolf||Zsolt Beothy-Elo||+3|
| Sven Efftinge, Frédéric Jouault
||Kathy Chan||Joel Cayne||+2|
|David Williams||David Williams||+2|