Archive freeze for 13.04

[Stéphane Graber]

Hello,

We're now approaching the final beta for the 13.04 release and so now is
around the time where we should think about freezing the archive.

In the past, we've usually started freezing with the second beta and
then kept everything frozen till release.


Now with the migration blocks that can be put in place in britney, it's
my opinion that we don't need to freeze the whole archive nearly that
early and so can save some time to the release team by not having nearly
as much to review as usual.

My proposal would therefore be to keep the archive unfrozen with a
transition block in place for beta2 effective this Thursday at 21:00
UTC, then remove the block next Thursday once beta2 is out and do a full
archive freeze the Thursday after that (11th) at the same time as the
KernelFreeze and NonLanguagePackTranslationDeadline.

So the timeline would look like:
 - 28th 21:00 UTC: FinalBetaFreeze, britney beta-2 block in place
 - 4th: Release of Beta-2, revert of the britney beta-2 block
 - 4th 21:00 UTC: DocumentationStringFreeze
 - 11th 21:00 UTC: KernelFreeze, NonLanguagePackTranslationDeadline and
full archive freeze.

Once in full archive freeze, the release team will carry the usual
package reviews as things land in the queue, unseeded packages will be
let through until we hit the unseeded packages freeze (do we have dates
yet?).


How does that proposal sound to the rest of the release team?

Do you think this is the right ratio between release team work and
archive stability?

Thanks

-- 
Stéphane Graber
Ubuntu developer
http://www.ubuntu.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 901 bytes
Desc: OpenPGP digital signature
URL: <https://lists.ubuntu.com/archives/ubuntu-release/attachments/20130325/547d8e90/attachment.pgp>