Europa Simultaneous Release
(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.)
The projects that plan to participate in the Europa Simultaneous Release are listed below, along with their milestone offsets and their project lead. Details about Jar Signing and Pack200 status as of M4 have been removed. FYI:
175367, 132450, 163421, 175284.
|Project||Project Lead(s)||Release Eng'g*||Offset||Ramp Down||Project Plan||Sign/Pack?**|
|AJDT||Matt Chapman||+1||AJDT 1.5|
|BIRT||Wenfeng Li||Xiaoying Gu||+2||Policy||BIRT 2.2.0||SJPD|
|CORONA||Dennis O'Flynn|| Pawel Kaczmarek,
|DLTK||Andrey Platov||Andrey Platov||+1||Ramp Down||DLTK 1.0||JP|
|DSDP DD||Doug Gaff||Ted Williams||+2||DD 0.9||DD 0.9|
|DSDP TM||Martin Oberhuber||+2||TM 2.0||TM 2.0||SJPD|
Model Base, SQL Tools)
|John Graham||+1||Policy||DTP 1.5|
|ECF||Scott Lewis||+1||Policy||ECF 1.0.0|
|Kevin Haaland|| Kim Moir,
|+0||3.3 endgame plan||3.3||SJPD|
|Dash (Eclipse Monkey)||Paul Colton||Ingo Muschenetz||+2||Policy||Project Plan|
|EMF||Ed Merks||Nick Boldt||+1||Policy|| 2.3
|MDT|| Kenn Hussey,
|Mylar progress||Mik Kersten||+1||Ramp down||Mylar 2.0|
|STP||Oisín Hurley||+2||STP Ramp Down||STP Europa Plan|
|Sri Doddapaneni||Hubert Leung||+2||Policy||TPTP 4.4||S J P|
| Web Tools Platform (WTP)
|David Williams||+2||WTP 2.0||WTP 2.0||JPD|
- * Add your name to this column if you need access to CVS to contribute to Europa features, and you're not already listed under Project Lead(s).
- ** There are four optimizing/conditioning tasks here. Place appropriate status codes S, J, P, D as appropriate: Signing, JarProcessor, Pack200, DigestBuilder
Testing Pre-Release builds via Policy Files
Projects can use policy files in the update manager to allow users to update against a different version of a plug-in than the one currently released. See Testing Pre-Release Builds Via Policy Files for more information.
Requirements For Participation
Projects that are part of Europa agree to abide by the following requirements.
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 Europa site will reference these sites, not replace them.
- moved to recommended
- Projects must use 4-part version numbers.
- eliminated due to bug 154505
- moved to recommended
- Any third-party plug-ins that are common between projects must be consumed via Orbit; the final Europa 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 "firstname.lastname@example.org"
- 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 Europa by the M4+0 date. Projects do so by adding themselves to the table/list above, along with their contact information.
- Projects that have demonstrated an inability to synchronize with Europa milestones by M6 will be removed from the Europa simultaneous release unless the remaining Europa projects vote to retain said project.
- 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.
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.
- Projects should 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 should use signed plugins using the Eclipse certificate.
- by M5: TPTP, WTP
- by M6: BIRT, DTP, EMF
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:
|M4||Dec 15||Dec 21|| |
|M5||Feb 9||Feb 16||Feb 23||Feb 24|
|M6 - API Freeze||Mar 23||Mar 30||Apr 6|
|M7 - RC0||May 4||May 11||May 18||May 22|
|RC1||May 18||May 23||May 25||May 29|
|RC2||May 25||May 30||Jun 5||Jun 7|
|RC3||Jun 8||Jun 13||Jun 14||Jun 15|
|RC4||Jun 15||Jun 20||Jun 21||Jun 22|
To avoid confusion amongst the various mailing lists in existence, Europa projects will use these lists:
- eclipse.org-planning-council  - the main list for the project leaders who are coordinating Europa
- cross-projects-issues-dev  - a list for developers and users who encounter problems with Europa: can't download, can't install, unable to make these two projects work together, etc.
- europa-build-workshop  - a list for the buildmeisters of Europa projects
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)(minutes)
Jan 3 - post-M4 (time)(minutes)
Jan 17 - post-M4 (time)(minutes)
Jan 23-24 - F2F @SFO (time)(minutes)
Feb 7 - pre-M5 (time)(minutes)
Feb 14 - mid-M5 (time)(minutes)
Feb 21 - mid-M5 (time)(minutes)
Mar 4 - F2F@EclipseCon post-M5 (time)(minutes)
Mar 21 - pre-M6 (time)- cancelled
Mar 28 - mid-M6 (time)(minutes)
Apr 4 - mid-M6 (time)
Apr 11 - post-M6 (time)(minutes)
May 2 - pre-RC0; plan for remaining RC calls (time)(minutes)
May 9 (time)
May 16 (time)(minutes)
- May 23(time)
- May 30 (time)
- June 6 Release Review (time)
- June 13 (time)
- June 20 (time)
- June 27 (time)
- IP Query
- All CQs must be submitted and prioritized by January 31st for Europa. This is a hard deadline.
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 Europa Build page (and old information on the Callisto build page).
The Europa Build page is where you go to learn how to add your project to the Europa build.