Beta2Freeze

Differences between revisions 2 and 3
⇤ ← Revision 2 as of 2009-09-22 19:03:32 →
Size: 794
Editor: 72-254-90-178
Comment:
← Revision 3 as of 2009-09-22 19:08:39 → ⇥
Size: 803
Editor: 72-254-90-178
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
For the preparation of the beta2 release (see BetaProcess), uploads for packages in `main` and `restricted` are held in the queue and are subject to manual approval of the release team. The purpose is to stabilize the archive, allow the archive administrators to consolidate it and fix [[https://wiki.ubuntu.com/UbuntuDevelopment#Consistency|package inconsistencies]], and be able to fix critical bugs quickly and in an isolated manner. For the preparation of the beta2 LTS release (see BetaProcess), uploads for packages in `main` and `restricted` are held in the queue and are subject to manual approval of the release team. The purpose is to stabilize the archive, allow the archive administrators to consolidate it and fix [[https://wiki.ubuntu.com/UbuntuDevelopment#Consistency|package inconsistencies]], and be able to fix critical bugs quickly and in an isolated manner.
Line 3: Line 3:
All exceptions require the approval of the release manager (see FreezeExceptionProcess), which is generally only granted if the upload fixes a bug which is milestoned for the beta release and does not have any unrelated intrusive changes. All exceptions require the approval of the release manager (see FreezeExceptionProcess), which is generally only granted if the upload fixes a bug which is milestoned for the beta2 LTS release and does not have any unrelated intrusive changes.

For the preparation of the beta2 LTS release (see BetaProcess), uploads for packages in main and restricted are held in the queue and are subject to manual approval of the release team. The purpose is to stabilize the archive, allow the archive administrators to consolidate it and fix package inconsistencies, and be able to fix critical bugs quickly and in an isolated manner.

All exceptions require the approval of the release manager (see FreezeExceptionProcess), which is generally only granted if the upload fixes a bug which is milestoned for the beta2 LTS release and does not have any unrelated intrusive changes.

Once the Beta2Release is shipped, we roll back to FeatureFreeze, UserInterfaceFreeze, and KernelFreeze status.

Beta2Freeze (last edited 2009-10-07 21:38:29 by 99-156-85-10)