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

Difference between revisions of "Europa Simultaneous Release"

(Projects)
(Milestones and Release Candidates)
Line 78: Line 78:
 
<table border=1 align=center>
 
<table border=1 align=center>
 
<tr><td>    </td><th>  +0  </th><th>  +1  </th><th>  +2  </th></tr>
 
<tr><td>    </td><th>  +0  </th><th>  +1  </th><th>  +2  </th></tr>
<tr><th> M4 </th><td> Dec 15 </td><td> Dec 21 </td><td> Dec 28 </td></tr>
+
<tr><th> M4 </th><td> Dec 15 </td><td> Dec 21 </td><td> Jan 4  </td></tr>
 
<tr><th> M5 </th><td> Feb  9 </td><td> Feb 16 </td><td> Feb 23 </td></tr>
 
<tr><th> M5 </th><td> Feb  9 </td><td> Feb 16 </td><td> Feb 23 </td></tr>
 
<tr><th> M6 - API Freeze </th>
 
<tr><th> M6 - API Freeze </th>
Line 88: Line 88:
 
<tr><th> Europa </th><td colspan=3> June 29 </td></tr>
 
<tr><th> Europa </th><td colspan=3> June 29 </td></tr>
 
</table>
 
</table>
 +
 
===Conference Calls===
 
===Conference Calls===
 
Wednesdays, 7am PT, 10am ET, 4pm CET, 5pm IT. ''613.287.8000 or 866.362.7064 passcode 874551#''
 
Wednesdays, 7am PT, 10am ET, 4pm CET, 5pm IT. ''613.287.8000 or 866.362.7064 passcode 874551#''

Revision as of 09:54, 20 October 2006

(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: (and their milestone offsets 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 build process maturity and 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.
  4. Project representatives must attend the planning meetings and conference calls - you have to be involved to be involved.

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.
  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. Should have new & noteworthy for each milestone. Should be something readable and usable not just a static list of all the bugs.

Recommended

These are suggested to the participating projects:

  1. (none yet)

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.
  4. Projects should provide both run-times and SDKs through their update sites and thence through the Europa update site.
  5. Must have ISV documentation.
  6. Must have user documentation.
  7. Something about consistency around product/primary feature plug-ins.
  8. Something about distinguishing the maturity levels of the different projects.
  9. Projects must use signed plugins using the Eclipse certificate.
  10. At least one person from each project must subscribe to cross-project bug inbox
  11. 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
  12. Common plug-ins must be used via Orbit; no duplication allowed
  13. Source tarballs will be created for Linux with build scripts
  14. Projects will volunteer to help with staffing multiple central buildmeisters
  15. Process/procedure/mechanism for the releasing end-game will be documented on the wiki
  16. Written process for withdrawing a project that cannot/does not meet the requirements
  17. Choose dates so that it is all done in advance - not at the last minute.
  18. Participate in a collective New & Noteworthy
  19. Projects should follow the Version Numbering policy.
  20. Optimize your update site using pack200 to reduce bandwidth utilization and provide a better update experience for users.
  21. Join (milestone releases according to schedule) by M4.
  22. Require that projects provide build RSS feeds as per the build workshop.
  23. We expect milestones to be consumed so fatal problems should be fixed and rebuilt, but problems in release candidates will just roll over to the next candidate.
  24. Project plan must list all the plug-ins and their required JVM versions by milestone M5.

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:

+0 +1 +2
M4 Dec 15 Dec 21 Jan 4
M5 Feb 9 Feb 16 Feb 23
M6 - API Freeze Mar 23 Mar 30 Apr 6
M7 - RC0 May 4 May 11 May 18
RCn...
RCX Jun 15  ?  ?
Europa June 29

Conference Calls

Wednesdays, 7am PT, 10am ET, 4pm CET, 5pm IT. 613.287.8000 or 866.362.7064 passcode 874551#

  • October 18 - Finalize rules and dates (time)
  • December 20 - mid-M4 (time)
  • Jan 3 - post-M4 (time)
  • Jan 23-24 - F2F @SFO (time)
  • Feb 7 - pre-M5 (time)
  • Feb 14 - mid-M5 (time)
  • Feb 21 - mid-M5 (time)
  • Mar 4 - F2F@EclipseCon post-M5 (time)
  • Mar 21 - pre-M6 (time)
  • Mar 28 - mid-M6 (time)
  • Apr 4 - mid-M6 (time)
  • Apr 11 - post-M6 (time)
  • May 2 - pre-RC0; plan for remaining RC calls (time)
  • May 9 - mid-RC0 (time)
  • May 16 - mid-RC0 (time)
  • May 23 - post-RC0 (time)
  • June 6 - pre-RCX (time)
  • June 13 - mid-RCX (time)
  • June 20 - mid-RCX (time)
  • June 27 - final RCX (time)

Back to the top