Modeling Project Ramp Down Policy/Ganymede
Ramp Down for Ganymede
This ramp down policy applies to those Modeling projects & selected components taking part in the Ganymede release of Eclipse projects. Currently, the following projects are included. Click links below for detailed list of components and their team leads.
|Eclipse Modeling Framework||EMF||+1 week (or less) from platform|
|Eclipse Modeling Framework Technologies||EMFT||+1 to +3 weeks from platform|
|Graphical Modeling Framework||GMF||+2 weeks from platform|
|Model Development Tools||MDT||+1 to +3 weeks from platform|
|Model To Model||M2M||+2 weeks from platform|
|Model To Text||M2T||+2 to +3 weeks from platform|
For reference, see Ganymede Simultaneous Release, in particular the Milestones and Release Candidates. In the case of Modeling projects, the dates below represent the last (+2 week) project release dates. +1 week projects (e.g. EMF) are expected the prior week in accordance with the schedule above.
Note that while these staggered dates apply to early development milestones, as Release Candidates are produced the time in between should naturally decrease until the final 'simultaneous' release on June 25th.
Ramp Down Details
Typically the last week of a Milestone is for testing, and fixing only regressions and P1 or blocking defects. For M6, we plan to be functionally and API complete and the remaining Release Candidates are (only) for fixing bugs, or fixing release required items (such as version numbers, licensing, etc.). Up to this point, Committers are expected to follow the normal Eclipse development practices when committing code.
For M7/RC0 to RC1, we expect each component lead (or delegate) to review and verify their teams' bugs.
After RC1 is produced, the time for general functional improvements is long past. The following describes the types of bugs that would be appropriate:
- A regression
- A P1 or P2 bug, one that is blocking or critical, and some cases of major severities.
- Documentation and PII files are exceptions to the normal PMC required review, since there is little chance of that breaking anything, though it is still expected to be complete by M6, and remaining work to be only documentation fixes (that is, no refactoring of plugins, build changes, etc, without PMC review and approval).
- In addition to a bug meeting the above priority/severity conditions, there should be a simple, safe, well understood fix that is well isolated from effecting other components, that doesn't affect API or adopters, that has been well reviewed and well tested.
- As each Release Candidate passes, the criteria for weighing the benefit-to-risk ratio criteria gets higher and higher, and as such requires a larger number of PMC members to review. As it is the Modeling project's practice to have each Project Lead on the PMC, getting approval to required fixes through RC2 should involve minimal overhead.
- After RC1: At least 1 PMC member (typically, the Project Lead) must review and vote + using the Bugzilla flag feature (see below).
- After RC2: Another Committer from the component or project and at least 1 PMC member must review and vote +1 after reviewing the bug for appropriateness and risk.
- After RC3: Two additional Committers and at least 2 PMC members must review and vote +1 after reviewing the bug for appropriateness and risk.
- June 13-18: Do zip, update, site preparations
- June 23: EPP Release
- June 24: Internal Release (Server Freeze)
- June 25: Public Release
Bugzilla Usage for RC Fixes
Committers can signify their approval for submitting fixes as required after RC2 by simply indicating +1 in a comment.
Bugzilla has a flag feature that is to be used for obtaining PMC approval. Enter the email address of the PMC member you are requesting approval from and submit. The PMC member is notified via email and will change the flag from '?' to '+' or '-' as appropriate.