BetaFreeze

Differences between revisions 7 and 8
⇤ ← Revision 7 as of 2008-08-06 16:22:45 →
Size: 819
Editor: localhost
Comment: converted to 1.6 markup
← Revision 8 as of 2012-09-02 22:07:27 → ⇥
Size: 1111
Editor: 24-148-91-163
Comment: Fix language to reflect that affecting images is the criteria for approval/release coordination instead of the main/restricted;universe/multiverse split
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
For the preparation of the beta 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 beta release (see BetaProcess), all uploads are held in the queue and are subject to manual approval of the release team. Packages that affect images that will be shipping for this milestone require release team approval before uploading. One can use the seeded-in-ubuntu tool from ubuntu-dev-tools to help figure out if a package will affect an image. Packages that do not affect images will generally be waved through the queue as time permits.

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 beta release (see BetaProcess), all uploads are held in the queue and are subject to manual approval of the release team. Packages that affect images that will be shipping for this milestone require release team approval before uploading. One can use the seeded-in-ubuntu tool from ubuntu-dev-tools to help figure out if a package will affect an image. Packages that do not affect images will generally be waved through the queue as time permits.

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 beta release and does not have any unrelated intrusive changes.

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