Sarge is frozen Sarge is frozen

Post by F » Wed, 18 May 2005 11:47:42

ello world,

Anthony Towns has committed a minor change to the britney script which
manages updates of packages to testing, and as a result packages are no
longer being accepted into testing without hand-approval by a member of
the release team.

Wait, that didn't come out quite right. Let's try again.

Sarge is now frozen! Wheeeeeee!!!

Thanks are due to everyone who has helped get us to this point: in
particular our ftpmasters, Anthony Towns, James Troup, and Ryan Murray,
for their continued dedication which has made it possible for mortals to
wrangle behemoths such as the 9,000-package sarge; our co-wranglers, the
release assistants Andreas Barth, Frank Lichtenheld, and Joey Hess; and
you, gentle maintainer, for your support and patience.

For those maintainers whose packages were unprepared for a freeze at
this moment (the process has, after all, been a long one), you still
have one last opportunity to get things into shape if there are any
remaining important problems. Read on.

Now to explain what, exactly, we mean by "freeze". The base freeze
upload policy of uploading changes in through unstable if you can,
and testing-proposed-updates if you must, has worked well (or so is the
subjective opinion of the release team), so we plan to continue to apply
the same policy for the freeze of the rest of the archive.

This means that, for all packages that still need to be updated for
sarge, the rules are as follows:

- If your package needs to be updated for sarge, and the version in
unstable doesn't contain extraneous changes (e.g, the version is the
same between testing and unstable), please upload your fix to
unstable and contact XXXX@XXXXX.COM .

- If the version in unstable already includes significant changes not
related to the bug to be fixed, contact debian-release about
uploading to testing-proposed-updates. Changed dependencies, new
upstream versions, changed library names, and completely rewriting
the packaging are "significant changes". So are lots of other

- If the version in unstable won't reach testing because of new
library dependencies, contact debian-release about uploading to

- If in doubt, contact debian-release first.

- In all cases, when preparing an upload please do not make changes to
the package that are not related to fixing the bugs in question.
Doing so makes it more time consuming for the release team to review
and approve such requests, delaying the release. It also delays the
fix for your package, because you will be asked to reupload.

- When contacting the release team, please explain why you are
requesting an update. Bug numbers are a must. The more we can
figure out from your first email and your changelog (if any), the
more quickly we can get your update in.

- If you have a package that needs updating, *please* don't forget to
contact us. *Don't expect us to find out about it on our own*.
Putting a comment in the changelog is not contacting the release
team. :) (This has happened at least a couple of times during the
base freeze; it's not a very good way of getting your package
approved quickly.)

Now, so as not to have everyone contact us at once about packages we
know we won't approve, here are the guidelines for changes that will be
accepted int