Release Change Control and Release Metrics

Phase Criteria for starting this Phase Change Control Process used in this Phase Criteria for exiting this Phase Next Phase
FC Conclusion of last Beta None/Low
  • Zero open critical tickets
  • All major tickets should be reviewed and priorities adjusted as needed
  • As many major tickets as possible should be fixed, but open major tickets will not be consider a blocker for starting the next project phase
  • minor tickets should be fixed, but open minor tickets will not be considered a blocker for starting the next project phase.
RC1
RC1 Zero open critical tickets
  • Only critical tickets may be fixed in this phase
  • Maintainers review tickets and decided what critical tickets should be fixed.
  • TLC only steps in to address any escalations
  • 2 weeks of testing minimum
  • Zero open critical tickets
  • 1 weeks of testing with zero new critical tickets being reported
  • RC2 if changes were made in RC1
  • GA if no changes in RC1
RC2 Successful exit from previous RC
  • Only critical tickets may be fixed in this phase
  • Maintainers review tickets and decided what critical tickets should be fixed.
  • TLC only steps in to address any escalations

 

  • 1 week or more of testing
  • Zero open critical tickets
  • 3 days of testing with zero new critical tickets being reported

 

  • RC<n+1> if changes were made in RC<n>
  • GA if no changes in RC<n>

 

RC<n> Successful exit from previous RC
  • Only critical tickets may be fixed in this phase
  • Maintainers review tickets and decided what critical tickets should be fixed.
  • TLC only steps in to address any escalations
  • 1 week or more of testing
  • Zero open critical tickets
  • 3 days of testing with zero new critical tickets being reported

 

  • RC<n+1> if changes were made in RC<n>
  • GA if no changes in RC<n>

 

Last modified by jfournier, 03/16/11 18:18:06 (14 months ago)