Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Europa Simultaneous Release

Revision as of 20:02, 21 August 2006 by Bjorn.eclipse.org (Talk | contribs)

(This is the easily-community modifiable wiki page about the Europa 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 Europa Simultaneous Release are:

Europa CVS Projects

A number of utilities have been written to automate the assembly of Callisto (and now Europa) 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 Callisto build page.

Requirements For Participation

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

Must Do

These are required for participation:

  1. The projects must work together.
  2. Projects must have their own functional project update site - the Europa site will reference these sites, not replace them.
  3. Projects must use 4-part version numbers. However we also need to define what the semantics of the 4-parts are: when do the parts get updated.

Should Do

These are strongly 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.

Recommended

These are suggested to the participating projects:

Not Sure Yet

These are ideas that we (individually or collectively) have had and we (collectively) have not yet decided whether to incorporate them.

  1. (From Callisto) Projects must use ICU4J.
  2. (From Callisto) Projects must use capabilities. The problem with this requirement was the vagueness of what it meant to "use capabilities".
  3. (From Callisto) Projects should have a written ramp down policy.

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.

Back to the top