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.
MemoryAnalyzer/Ramp Down Plan
< MemoryAnalyzer
Revision as of 05:12, 23 October 2019 by Andrew johnson.uk.ibm.com (Talk | contribs) (→Ramp down plan)
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 M3 [was M7 for Photon and before], 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 [was RC1 and RC2 for Photon and before] only bug fixes 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, including adding new and noteworthy
For RC2 [was RC3 - RC4 for Photon and before] only bug fixes damaging the build/functionality of the simultaneous release should are allowed
- Galileo Simultaneous Release
- Helios Simultaneous Release
- Indigo Simultaneous Release
- Juno/Simultaneous Release Plan
- Kepler/Simultaneous Release Plan
- Luna/Simultaneous Release Plan
- Mars/Simultaneous Release Plan
- Neon/Simultaneous Release Plan
- Oxygen/Simultaneous Release Plan
- Photon/Simultaneous Release Plan
- Simultaneous Release subsequent releases on a 13-week cycle