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 "MemoryAnalyzer/Ramp Down Plan"
| Line 17: | Line 17: | ||
* [[Galileo Simultaneous Release]] | * [[Galileo Simultaneous Release]] | ||
* [[Helios Simultaneous Release]] | * [[Helios Simultaneous Release]] | ||
| − | + | * [[Indigo Simultaneous Release]] | |
[[Category:MemoryAnalyzer]] | [[Category:MemoryAnalyzer]] | ||
Revision as of 09:11, 27 May 2011
Ramp down plan
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.
For M7, we plan to be API and feature complete, so there will be no breaking API changes and no new feature requests will be accepted.
For RC1 - RC2 only bugfixes to Memory Analyzer functionaliry should be done. The following describes the types of bugs that would be appropriate:
- A regression
- A P1 or P2 bug, one that is blocking or critical
- Minor documentation changes
For RC3 - RC4 only bugfixes damaging the build/functionality of the simultaneous release should are allowed