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.
Difference between revisions of "Europa Simultaneous Release"
(→Not Sure Yet) |
(→Requirements For Participation) |
||
| Line 33: | Line 33: | ||
====Recommended==== | ====Recommended==== | ||
These are suggested to the participating projects: | These are suggested to the participating projects: | ||
| + | # (none yet) | ||
====Not Sure Yet==== | ====Not Sure Yet==== | ||
| Line 43: | Line 44: | ||
# Something about distinguishing the maturity levels of the different projects. | # Something about distinguishing the maturity levels of the different projects. | ||
# Projects must use signed plugins using the Eclipse certificate. | # Projects must use signed plugins using the Eclipse certificate. | ||
| + | # At least one person from each project must subscribe to cross-project bug inbox | ||
| + | # 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 | ||
| + | # Common plug-ins must be used via Orbit; no duplication allowed | ||
| + | # Source tarballs will be created for Linux with build scripts | ||
| + | # Projects will volunteer to help with staffing multiple central buildmeisters | ||
| + | # Process/procedure/mechanism for the releasing end-game will be documented on the wiki | ||
| + | # Written process for withdrawing a project that cannot/does not meet the requirements | ||
| + | # Choose dates so that it is all done in advance - not at the last minute. | ||
===Milestones and Release Candidates=== | ===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. | 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. | ||
Revision as of 21:14, 30 September 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.)
Contents
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:
- The projects must work together.
- Projects must have build process maturity and their own functional project update site - the Europa site will reference these sites, not replace them.
- 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.
- 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:
- 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.
- 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.
Recommended
These are suggested to the participating projects:
- (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.
- (From Callisto) Projects must use ICU4J.
- (From Callisto) Projects must use capabilities. The problem with this requirement was the vagueness of what it meant to "use capabilities".
- (From Callisto) Projects should have a written ramp down policy.
- Projects should provide both run-times and SDKs through their update sites and thence through the Europa update site.
- Something about consistency around product/primary feature plug-ins.
- Something about distinguishing the maturity levels of the different projects.
- Projects must use signed plugins using the Eclipse certificate.
- At least one person from each project must subscribe to cross-project bug inbox
- 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
- Common plug-ins must be used via Orbit; no duplication allowed
- Source tarballs will be created for Linux with build scripts
- Projects will volunteer to help with staffing multiple central buildmeisters
- Process/procedure/mechanism for the releasing end-game will be documented on the wiki
- Written process for withdrawing a project that cannot/does not meet the requirements
- Choose dates so that it is all done in advance - not at the last minute.
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.