Jump to: navigation, search

Difference between revisions of "Europa Simultaneous Release"

(Projects)
(Projects)
Line 16: Line 16:
 
| [http://www.eclipse.org/cdt/ CDT] || Doug Schaefer || || +1  
 
| [http://www.eclipse.org/cdt/ CDT] || Doug Schaefer || || +1  
 
|-
 
|-
| [http://www.eclipse.org/corona/ CORONA] || Dennis O'Flynn || Pawel Kaczmarek,<br/>Marcin Okraszewski || +2 || || [[Corona_Plan|v1.0]] || Y (M6)
+
| [http://www.eclipse.org/corona/ CORONA] || Dennis O'Flynn || Pawel Kaczmarek,<br/>Marcin Okraszewski || +2 || || [[Corona_Plan|v1.0]] || Y (M6) || N
 
|-
 
|-
 
| [http://www.eclipse.org/dltk DLTK] || Andrey Platov || || +1 || || [http://wiki.eclipse.org/index.php/DLTK_Project_Plan DLTK 1.0]
 
| [http://www.eclipse.org/dltk DLTK] || Andrey Platov || || +1 || || [http://wiki.eclipse.org/index.php/DLTK_Project_Plan DLTK 1.0]

Revision as of 10:05, 14 March 2007

(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 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 E-U/Ext?** Egs/Ext?***
AJDT Matt Chapman +1

AJDT 1.5

BIRT Wenfeng Li +2 BIRT 2.2.0
Buckminster Thomas Hallgren +1
CDT Doug Schaefer +1
CORONA Dennis O'Flynn Pawel Kaczmarek,
Marcin Okraszewski
+2 v1.0 Y (M6) N
DLTK Andrey Platov +1 DLTK 1.0
DSDP DD Doug Gaff Ted Williams +2 DD 0.9 DD 0.9
DSDP TM Martin Oberhuber +2 TM 2.0 TM 2.0 Y (M5) N (on
UM Site)
DTP
(Connectivity, Enablement,
Model Base, SQL Tools)
John Graham +1 Policy DTP 1.5 Y (M5) N
ECF Scott Lewis +1 ECF 1.0.0
Eclipse
(Equinox, Platform,
JDT, PDE)
Kevin Haaland +0 3.3
Dash (Eclipse Monkey) Paul Colton Ingo Muschenetz +2
EMF Ed Merks +1 Policy 2.3 Y N (on
UM Site)
EMFT
(Query,
Transaction,
Validation)
Christian Damus +1 Policy 1.1 Y Y
EMFT
(JET)
Paul Elder +1 Policy
GEF Anthony Hunter +1
GMF Richard Gronback +2 Policy 2.0 N N
MDT Kenn Hussey,
Christian Damus,
Michael Golubev,
Lei Zhang
+2 Policy MDT 1.0 OCL: Y OCL: Y
Mylar progress Mik Kersten +1 Mylar 2.0
STP Oisín Hurley +2 STP Ramp Down STP Europa Plan
TPTP
(Monitoring, Performance,
Platform, Test)
Sri Doddapaneni Hubert Leung +2 TPTP 4.4
Web Tools Platform (WTP)

WST
JST
JSF
Dali(JPA)

Tim Wagner

David Williams
Naci Dai
Raghunathan Srinivasan
Neil Hauge

David Williams +2 WTP 2.0 WTP 2.0
* 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).
** Please place a 'Y' in this column if, as per the Planning Council Minutes, your project's features include the words "end-user" and "extender". See also bug 173276
*** Please place a 'Y' in this column if, as per the Planning Council Minutes, your project will include examples as part of the "extender" version. See also bug 173276

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.

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 Europa site will reference these sites, not replace them.
  3. 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.
  4. Projects must use 4-part version numbers.
  5. Projects must provide both run-times and SDKs through their update sites and thence through the Europa update site. (The Planning Council identified that this might not be technically possible due to bugs in the update manager's computation of required dependencies. We will remove this requirement if it proves to be impossible.)
  6. Projects must use signed plugins using the Eclipse certificate.
    1. by M5: TPTP, WTP
    2. by M6: BIRT, DTP, EMF
  7. 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).
  8. 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].
  9. Project representatives must attend the planning meetings and conference calls - you have to be involved to be involved.
  10. 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"
  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. 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.
  13. 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.
  14. 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.)
  15. Projects must have their IP approved (a normal Eclipse requirement) and will follow the Eclipse Legal deadlines to do so.

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
M4 Dec 15 Dec 21 Jan 4 Feb 7 Feb 14Jan 5 Feb 14
M5 Feb 9 Feb 16 Feb 23 Feb 24
M6 - API Freeze Mar 23 Mar 30 Apr 6 Apr 7
M7 - RC0 May 4 May 11 May 18 May 19
RCn...
RCX Jun 15  ?  ?
Europa June 29

Mailing Lists

To avoid confusion amongst the various mailing lists in existence, Europa 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 Europa: 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

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

RSVPs for Mar 4 - F2F@EclipseCon meeting

  1. Nick Boldt
  2. Rich Gronback
  3. Thomas Hallgren
  4. Henrik Lindberg (if flight arrives in time)
  5. Harm Sluiman (substituting for Sri)
  6. Paul Styles
  7. Christian Damus
  8. Martin Oberhuber

Regrets:

  1. Doug Schaefer (flight arrives too late)
  2. Yossi Leon (arriving later in the week)
  3. Kim Moir (arriving later in the week)

IP Schedule

  • IP Query
  • All CQs must be submitted and prioritized by January 31st for Europa. This is a hard deadline.

Europa Builds

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.