Ganymede Simultaneous Release
The projects that plan to participate in the Ganymede Simultaneous Release are listed below, along with their milestone offsets and their project lead.
|Project||Project Lead(s)||Release Eng'g*||Offset|
|DSDP TM||Martin Oberhuber||+2|
|EMF||Ed Merks||Nick Boldt||+1|
|GMF||Richard Gronback||Max Feldman||+2|
|MDT||Kenn Hussey||Nick Boldt||+2|
|TPTP (Platform, Test, Trace, Monitoring)||Joanna Kubasta||Joel Cayne||+2|
|[EMFT Search]||Lucas Bigeardel||Lucas Bigeardel||+2|
Requirements For Participation
Projects that are part of Ganymede agree to abide by the following requirements. Unlike the somewhat lax enforcement of previous years, the EMO will remove projects that do not meet the required constraints.
Two Classes of Participation
One thing we are considering for Ganymede is to have two classes of participation:
- High Fidelity - projects that agree to coordinate their efforts at some higher level; perhaps common user interface efforts? abiding by the user interface guidelines? joining their APIs? dedicated cross-project testing?
- Simultaneous Release - simultaneous release like we had with Callisto and Europa
These are required for participation:
- The projects must work together. This means that one should be able to load any subset of the Europa projects into Eclipse and each of the loaded projects should be able to pass all the same tests as if it had been loaded independently.
- Projects must have build process maturity and their own functional project update site - the Ganymede site will reference these sites, not replace them.
- Projects must use 4-part version numbers.
- Any third-party plug-ins that are common between projects must be consumed via Orbit; the final Ganymede release will not have duplicate third-party libraries (note that this only applies to identical versions of the libraries; thus if project A requires foo.jar 1.6 and project B uses foo.jar 1.7, that's ok).
- All plug-ins must correctly list their required JVM versions in the manifest/plugin.xml. See the wiki page about selecting the correct JVM .
- Project representatives must attend the planning meetings and conference calls - you have to be involved to be involved.
- At least one person from each project must subscribe to cross-project bug inbox, i.e. edit Bugzilla prefs to watch "email@example.com"
- Build team members from each project will provide communication channels: phone, mail, IM, IRC and will be available during to-be-specified crucial integration times
- Projects must have stated and demonstrated their intent to join Ganymede by the M4+0 date. Projects do so by adding themselves to the table/list above and to the Ganymede common build infrastructure.
- Projects should have a written ramp down policy. (One of the issues identified with this guideline is that its not so much the ramp down policy of how many votes are needed for each bug fix that we need to be consistent on, but rather the meaning of each of the milestones and release candidates. Here  is the Platform 3.2 ramp down policy as a guideline for other projects.)
- Projects must have their IP approved (a normal Eclipse requirement) and will follow the Eclipse Legal deadlines to do so.
- Projects must optimize their update site using pack200 to reduce bandwidth utilization and provide a better update experience for users. Additionally, they should do site digesting.
- Projects must use signed plugins using the Eclipse certificate.
- Projects must have download and installed sizes declared in their feature.
These are recommended for participating projects:
- Projects should have jar'ed plug-ins because this is good Eclipse citizenship.
- Projects should use Eclipse message bundles, not Java bundles because this is a good Eclipse citizenship. (see Message Bundle Conversion Tool and )
- Build reproducibility? Require that projects be buildable by community members. Should be identical bits (but not required). All build assets and documentation in CVS/Subversion.
- Non-project-team-members should be able to build each project.
- Non-project-team-members should be able to run unit tests on each project.
- Source tarballs should be created for Linux distros to build with.
- Should have new & noteworthy for each milestone. Should be something readable and usable not just a static list of all the bugs. Corollary: individual new & noteworthy should be linked in to the collective New & Noteworthy.
- Projects should use ICU4J when appropriate.
- Projects should provide build RSS feeds as per the build workshop.
Milestones and Release Candidates
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 EPP 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.
|M2||Sep 21||Sep 26||Oct 3||Oct 5||Oct 9|
|M3||Nov 2||Nov 7||Nov 14||Nov 16||Nov 20|
|M4||Dec 14||Dec 19||Jan 6||Jan 8||Jan 11|
|M5||Feb 8||Feb 13||Feb 20||Feb 22||Feb 26|
|M6 - API Freeze|
|M7 - RC0|
Eclipse projects have three communication channels: a mailing list for developers, a newsgroup for users, and Bugzilla. Ganymede, although not a "project" per se, will use the same structure:
- cross-projects-issues-dev  - mailing list for developers and releng
- eclipse.simultaneous-release (TBC) - newsgroup for users
- bugzilla (new & search) Eclipse Foundation > Community > Cross-Project
The old eclipse.org-planning-council  mailing list will be used for non-Ganymede Planning Council items
Information on the Gan-o-matic build system is under development.
- EMF would like Gan-o-matic to retrieve files from a different location than it uses to set up site.xml so that they can have a different url for the site.xml that does download tracking.