Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "MemoryAnalyzer/Ramp Down Plan"
(→See Also) |
m (→Ramp down plan) |
||
Line 6: | Line 6: | ||
'''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 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''' | + | '''For RC1 - RC2 only bugfixes to Memory Analyzer''' functionality should be done. The following describes the types of bugs that would be appropriate: |
* A regression | * A regression | ||
* A P1 or P2 bug, one that is blocking or critical | * A P1 or P2 bug, one that is blocking or critical |
Revision as of 03:15, 5 June 2013
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 functionality 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