From ee1ac48aaa5c3c252a4b7733df537a67d19a827d Mon Sep 17 00:00:00 2001 From: hertzog Date: Mon, 9 Jul 2012 07:30:47 +0000 Subject: [PATCH] Document the existence of "hints" that release managers can use Mention how they use hints to tweak the conditions of testing migration. Drop some outdated/uninteresting information at the same time. Closes: #679562 Based-on-patch-by: Paul Gevers git-svn-id: svn://anonscm.debian.org/ddp/manuals/trunk/developers-reference@9255 313b444b-1b9f-4f58-a734-7bb04f332e8d --- debian/changelog | 5 ++++- pkgs.dbk | 26 +++++++++++++++++--------- 2 files changed, 21 insertions(+), 10 deletions(-) diff --git a/debian/changelog b/debian/changelog index 7c16abd..4b0ee6c 100644 --- a/debian/changelog +++ b/debian/changelog @@ -7,8 +7,11 @@ developers-reference (3.4.9) UNRELEASED; urgency=low Thanks to Per Andersson and Steve Langasek for the patch. * Recommend usage of gender-neutral formulations in README-contrib. * Fix Vcs-Browser URL. Thanks to Charles Plessy who spotted it. + * Document the existence of "hints" that release managers can + use to tweak the conditions of testing migration. Closes: #679562 + Thanks to Paul Gevers for the patch. - * Translation updates (complete) + [ Translation updates ] - Japanese by Hideki Yamane. - French by David Prévot. diff --git a/pkgs.dbk b/pkgs.dbk index 3ce0bee..88bb6d8 100644 --- a/pkgs.dbk +++ b/pkgs.dbk @@ -2386,9 +2386,7 @@ the following: The package must have been available in unstable for 2, 5 or 10 days, depending on the urgency (high, medium or low). Please note that the urgency is sticky, meaning that the highest urgency uploaded since the -previous testing transition is taken into account. Those -delays may be doubled during a freeze, or testing -transitions may be switched off altogether; +previous testing transition is taken into account; @@ -2416,7 +2414,13 @@ It must not break any dependency of a package which is already available in The packages on which it depends must either be available in testing or they must be accepted into testing at the same time (and they will be if they fulfill -all the necessary criteria). +all the necessary criteria); + + + + +The phase of the project. I.e. automatic transitions are turned off during +the freeze of the testing distribution. @@ -2628,10 +2632,8 @@ If you are interested in details, this is how britney works: The packages are looked at to determine whether they are valid candidates. This gives the update excuses. The most common reasons why a package is not considered are too young, RC-bugginess, and out of date on some arches. For -this part of britney, the release managers have hammers of various sizes to -force britney to consider a package. (Also, the base freeze is coded in that -part of britney.) (There is a similar thing for binary-only updates, but this -is not described here. If you're interested in that, please peruse the code.) +this part of britney, the release managers have hammers of various sizes, +called hints (see below), to force britney to consider a package. Now, the more complex part happens: Britney tries to update testing @@ -2649,7 +2651,13 @@ url="http://&ftp-master-host;/testing/update_output/">. The hints are available via . +url="http://&ftp-master-host;/testing/hints/">, where you can find +the +description +as well. With the hints, the Debian Release team can block or unblock +packages, ease or force packages into testing, remove +packages from testing, approve uploads to +testing-proposed-updates or override the urgency. -- 2.30.2