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 "Dash Project/Ramp-Down Policy"
(→Ramp-Down for Europa) |
(→RC Plans =) |
||
| Line 9: | Line 9: | ||
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.). Post M6 will be for the addition of documentation and new scripts. | 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.). Post M6 will be for the addition of documentation and new scripts. | ||
| − | == RC Plans === | + | === RC Plans === |
From M6 to RC1 on May 18th, we expect each component lead (or delegate) to review and verify their teams' bugs. | From M6 to RC1 on May 18th, we expect each component lead (or delegate) to review and verify their teams' bugs. | ||
Revision as of 08:25, 2 May 2007
Ramp-Down for Europa
For reference, see the Europa Simultaneous Release, in particular the Milestones and Release Candidates. In the case of Dash projects, the dates below represent the last (+2 week) project release dates.
Typically the last week of a Milestone is for testing, and fixing only regressions and P1 or blocking defects. For milestones, the component lead (or delegate) is enough to review and approve a bug.
M6 Plans
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.). Post M6 will be for the addition of documentation and new scripts.
RC Plans
From M6 to RC1 on May 18th, we expect each component lead (or delegate) to review and verify their teams' bugs.
After the first RC is produced, other RCs will be produced, if needed, every week.
After the first RC 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.
- 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 affecting 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.
Schedule
- May 18th, RC 1 produced
- After the 18th, besides the normal component team review, at least 1 PMC member must also review and vote +1 after reviewing the bug for appropriateness and risk.
- June 22
- Do zip, update, site preparations
- June 29
- Release