This page is for developers of the June 2009 Galileo Simultaneous Release. Note that the master page on the eclipse.org site points here.





Simultaneous Release Preceded by

Ganymede Galileo

2009 Succeeded by

Helios





Project Plan

A roll up project plan for projects participating in the Galileo Simultaneous Release is found here: http://www.eclipse.org/projects/project-plan.php?projectid=galileo

Requirements For Participation

Projects that are part of Galileo agree to abide by the following requirements. Note: the EMO will remove projects that do not meet the required constraints.

For a report of overall Galileo status, see this report. Note: this report is bugzilla intensive, so please use sparingly.

Must Do

Should Do

These milestone and release candidate dates are based on the dependencies of the projects (we call these the +0, +1, and +2 dependencies). Obviously, if a +0 date slips, then it will cause the +1 and +2 dates to slip; similarly for a +1 slip causing +2 slips. Note that the +0, +1, +2, and +3 dates are roughly equivalent to stable nightly builds in a traditional Eclipse project - each of these partial milestone builds will incorporate more and more of the associated project milestones. The "Release" date is the official M/RC date.

Note: in the following table, RC5 on the 'Galileo' line does not mean this final build is a release 'candidate' ... it is still to be the 'final build' for this Release ... but 'RC5' is the suggested "target" to have some consistent terminology in Bugzilla, and similar things, to be able to mark things that are different in the final release build than in the RC4 build. [The full word, "Galileo" doesn't make a very good bugzilla milestone target, since it's a little too inclusive, and "R" (for "Release") is too short. TODO: next year consider "GA" for this final target?]

Hopefully there will not by ANY differences between RC4, and RC5 ... but, some projects may find they have to make doc additions, readme files, etc., so ... this just provides a way that such changes can be consistently marked, tracked, etc., to better keep everyone informed about what might be different between RC4 and the RC5 (the final released code). [Note: it's probably obvious, but this does not mean "RC5" should be part of the final zip file names or anything. those can still be what ever "final" name they would always have.]

The calendar is available in the following formats: ICal,ATOM News Feed,HTML

Communication

Cross-Project Milestone & RC Status Reporting

As with Ganymede, reporting on status will be done using a wiki table.

We have decided that instead of affirmative signoffs, projects should post exceptions to the cross-project dev mailing list.

Conference Calls

The Planning Council is the body responsible for coordinating the Galileo release train. Thus, its conference calls are the Galileo planning and coordination calls.

Mailing Lists and Newsgroups

Eclipse projects have three communication channels: a mailing list for developers, a newsgroup for users, and Bugzilla. Galileo, although not a "project" per se, will use the same structure:

cross-projects-issues-dev - mailing list for developers and releng (see archives)

eclipse.simultaneous-release - newsgroup for users (see archives)

The old eclipse.org-planning-council mailing list will be used for non-Galileo Planning Council items.

Bugs & Feature Requests

Search in Eclipse Foundation > Community > Cross-Project

Open a new Cross-Project bug

Galileo Builds and P2 repository

A number of utilities have been written to automate the assembly of Callisto '06, Europa '07, Ganymede '08 and now Galileo '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 Galileo Build page (with old information on the Ganymede Build and Europa Build pages).

And with Galileo we are using the Buckminster Galileo Builder.

The Contributing to Galileo Build page is where you go to learn how to add your project to the Galileo build.

p2 Repository

To obtain the latest published bits from Galileo, 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

SR1

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.

+0

Mon. +1

Tues. +2

Wed. +3

Thur. EPP

Fri. RC1 8/10 8/11 8/12 8/13 8/14 RC2 8/31 9/1 9/2 9/3 9/4 RC3 9/7 9/8 9/9 9/10 9/11 RC4 9/14 9/15 9/16 9/17 9/18 Galileo SR1 ("GA") promote: 9/24 GA: 9/25

SR2

2/26/10 (last Friday of February)

Rampdown similar to SR1.





+0

Mon. +1

Tues. +2

Wed. +3

Thur. EPP

Fri. RC1 1/18 1/19 1/20 1/21 1/22 RC2 2/1 2/2 2/3 2/4 2/5 RC3 2/8 2/9 2/10 2/11 2/12 RC4 2/15 2/16 2/17 2/18 2/19 Galileo SR2 ("GA") promote: 2/25 GA: 2/26

Projects

The projects that plan to participate in the Galileo Simultaneous Release are listed below, along with their milestone offsets, leaders, release engineer, and ramp down policy.