Skip to main content
Jump to: navigation, search

Difference between revisions of "MemoryAnalyzer/Ramp Down Plan"

(See Also)
(See Also)
Line 12: Line 12:
  
 
'''For RC3 - RC4''' only bugfixes damaging the build/functionality of the simultaneous release should are allowed
 
'''For RC3 - RC4''' only bugfixes damaging the build/functionality of the simultaneous release should are allowed
 
== See Also ==
 
  
 
* [[Galileo Simultaneous Release]]
 
* [[Galileo Simultaneous Release]]
Line 25: Line 23:
 
* [[Oxygen/Simultaneous Release Plan]]
 
* [[Oxygen/Simultaneous Release Plan]]
 
* [[Photon/Simultaneous Release Plan]]
 
* [[Photon/Simultaneous Release Plan]]
 +
* [[Simultaneous Release]] subsequent releases on a 13-week cycle
  
 
[[Category:Memory Analyzer]]
 
[[Category:Memory Analyzer]]

Revision as of 05:06, 23 October 2019

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

Back to the top