ReleaseCandidate

Differences between revisions 7 and 8
⇤ ← Revision 7 as of 2010-11-01 16:18:12 →
Size: 403
Editor: 99-191-111-134
Comment:
← Revision 8 as of 2013-04-19 05:30:51 → ⇥
Size: 555
Editor: adconrad
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
The release candidate is a production-quality pre-release one week before the final release. In an ideal world, it would be (functionally) identical to the final release. From here until FinalRelease, changes are only permitted at the release manager's discretion, and will only be allowed for very high-priority showstopper bugs that might justify delaying the release. During the week leading up to the final release, the images produced are all considered release candidates. In an ideal world, the first one would end up being the final release, however we don't live in an ideal world, and this week is used to shake out the last release critical bugs and get as much testing in as possible. From here until FinalRelease, changes are only permitted at the release team's discretion, and will only be allowed for very high-priority showstopper bugs that might justify delaying the release.

During the week leading up to the final release, the images produced are all considered release candidates. In an ideal world, the first one would end up being the final release, however we don't live in an ideal world, and this week is used to shake out the last release critical bugs and get as much testing in as possible. From here until FinalRelease, changes are only permitted at the release team's discretion, and will only be allowed for very high-priority showstopper bugs that might justify delaying the release.

See FreezeExceptionProcess.

ReleaseCandidate (last edited 2013-04-19 05:33:52 by adconrad)