Skip to main content
Jump to: navigation, search

Ganymede Simultaneous Release

Revision as of 15:00, 9 August 2007 by Bjorn.freeman-benson.eclipse.org (Talk | contribs) (New page: (This is the easily-community modifiable wiki page about the Ganymede Simultaneous Release. This page (and its siblings) should be the main developer information pages. [http://www.eclipse...)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

(This is the easily-community modifiable wiki page about the Ganymede Simultaneous Release. This page (and its siblings) should be the main developer information pages. The master page on the eclipse.org site mostly points here.)

Projects

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

Requirements For Participation

Projects that are part of Ganymede agree to abide by the following requirements.

Must Do

These are required for participation:

  1. 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.
  2. Projects must have build process maturity and their own functional project update site - the Ganymede site will reference these sites, not replace them.
  3. Projects must use 4-part version numbers.
  4. 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).
  5. All plug-ins must correctly list their required JVM versions in the manifest/plugin.xml. See the wiki page about selecting the correct JVM [1].
  6. Project representatives must attend the planning meetings and conference calls - you have to be involved to be involved.
  7. At least one person from each project must subscribe to cross-project bug inbox, i.e. edit Bugzilla prefs to watch "cross-project.inbox@eclipse.org"
  8. 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
  9. 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.
  10. 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 [2] is the Platform 3.2 ramp down policy as a guideline for other projects.)
  11. Projects must have their IP approved (a normal Eclipse requirement) and will follow the Eclipse Legal deadlines to do so.
  12. 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.
  13. Projects must use signed plugins using the Eclipse certificate.

Should Do

These are recommended for participating projects:

  1. Projects should have jar'ed plug-ins because this is good Eclipse citizenship.
  2. Projects should use Eclipse message bundles, not Java bundles because this is a good Eclipse citizenship. (see Message Bundle Conversion Tool and [3])
  3. 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.
  4. Non-project-team-members should be able to build each project.
  5. Non-project-team-members should be able to run unit tests on each project.
  6. Source tarballs should be created for Linux distros to build with.
  7. 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.
  8. Projects should use ICU4J when appropriate.
  9. 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.

Candidate milestone dates:

Staging Release
+0 +1 +2
M2 Sep 21 Sep 28 Oct 5 Oct 9
M3 Nov 2 Nov 9 Nov 16 Nov 20
M4 Dec 14 Dec 21 Jan 8 Jan 11
M5 Feb 8 Feb 15 Feb 22 Feb 26
M6 - API Freeze
M7 - RC0
RC1
RC2
RC3
RC4
Ganymede June 29

Mailing Lists

To avoid confusion amongst the various mailing lists in existence, Ganymede projects will use these lists:

  • eclipse.org-planning-council [4] - the main list for the project leaders who are coordinating Europa
  • cross-projects-issues-dev [5] - a list for developers and users who encounter problems with Ganymede: can't download, can't install, unable to make these two projects work together, etc.
  • europa-build-workshop [6] - a list for the buildmeisters of Europa projects

Conference Calls

Ganymede Builds

Information on the Gan-o-matic build system is under development.

Back to the top