From d80318035daccc476d53332cd904630b36147977 Mon Sep 17 00:00:00 2001 From: he Date: Sun, 1 Jun 2008 20:25:44 +0000 Subject: [PATCH] Update several bits about release management/testing transitions. git-svn-id: svn://anonscm.debian.org/ddp/manuals/trunk/developers-reference@5200 313b444b-1b9f-4f58-a734-7bb04f332e8d --- debian/changelog | 1 + pkgs.dbk | 35 ++++++++++++++++------------------- 2 files changed, 17 insertions(+), 19 deletions(-) diff --git a/debian/changelog b/debian/changelog index fa8d821..fb6a3b3 100644 --- a/debian/changelog +++ b/debian/changelog @@ -21,6 +21,7 @@ developers-reference (3.4.0) UNRELEASED; urgency=low doesn't exist anymore. * Fix several typesetting errors and typos noticed by Sandro Tosi, thanks for the notes! Closes: #483223 + * Update several bits about release management/testing transitions. -- Marc 'HE' Brockschmidt Sun, 01 Jun 2008 16:26:33 +0200 diff --git a/pkgs.dbk b/pkgs.dbk index 1f35c35..5494ef6 100644 --- a/pkgs.dbk +++ b/pkgs.dbk @@ -2193,8 +2193,8 @@ being a release candidate. Please see below for details. Updates from unstable The scripts that update the testing distribution are run -each day after the installation of the updated packages; these scripts are -called britney. They generate the +twice each day, right after the installation of the updated packages; these +scripts are called britney. They generate the Packages files for the testing distribution, but they do so in an intelligent manner; they try to avoid any inconsistency and to use only non-buggy packages. @@ -2268,7 +2268,7 @@ scripts. See below for details. Some further dependency analysis is shown on — but be warned, this page also +url="http://release.debian.org/migration/"> — but be warned, this page also shows build dependencies which are not considered by britney.
@@ -2458,11 +2458,13 @@ is not described here. If you're interested in that, please peruse the code.) Now, the more complex part happens: Britney tries to update testing - with the valid candidates; first, each package alone, and then -larger and even larger sets of packages together. Each try is accepted if -testing is not more uninstallable after the update than -before. (Before and after this part, some hints are processed; but as only -release masters can hint, this is probably not so important for you.) + with the valid candidates. For that, britney tries to add each +valid candidate to the testing distribution. If the number of uninstallable +packages in testing doesn't increase, the package is +accepted. From that point on, the accepted package is considered to be part +of testing, such that all subsequent installability +tests include this package. Hints from the release team are processed +before or after this main run, depending on the exact type. If you want to see more details, you can look it up on @@ -2566,7 +2568,8 @@ at &email-debian-release; and ask them to approve your upload. What are release-critical bugs, and how do they get counted? All bugs of some higher severities are by default considered release-critical; -currently, these are critical, grave, and serious bugs. +currently, these are critical, grave and +serious bugs. Such bugs are presumed to have an impact on the chances that the package will @@ -2576,16 +2579,10 @@ if a package has open release-critical bugs filed on it, it won't get into stable. -The unstable bug count are all release-critical bugs without -either any release-tag (such as potato, woody) or with release-tag sid; also, -only if they are neither fixed nor set to sarge-ignore. The testing - bug count for a package is considered to be roughly the bug count of -unstable count at the last point when the testing -version equalled the unstable version. - - -This will change post-sarge, as soon as we have versions in the bug tracking -system. +The unstable bug count are all release-critical bugs which +are marked to apply to package/version + combinations that are available in unstable for a release +architecture. The testing bug count is defined analogously.
-- 2.30.2