From b371924c48cc2132db092d34c6c853d55f411f0c Mon Sep 17 00:00:00 2001 From: aba Date: Wed, 8 Jun 2005 12:14:38 +0000 Subject: [PATCH] adjust information about distributions with reality git-svn-id: svn://anonscm.debian.org/ddp/manuals/trunk/developers-reference@3389 313b444b-1b9f-4f58-a734-7bb04f332e8d --- debian/changelog | 7 +++++++ developers-reference.sgml | 24 +++++++++++++++--------- 2 files changed, 22 insertions(+), 9 deletions(-) diff --git a/debian/changelog b/debian/changelog index 0a1bc2c..1582380 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +developers-reference (3.3.7) unstable; urgency=low + + * Andreas Barth: + - adjust information about distributions with reality. + + -- Andreas Barth Wed, 8 Jun 2005 06:13:48 -0600 + developers-reference (3.3.6) unstable; urgency=low * Andreas Barth diff --git a/developers-reference.sgml b/developers-reference.sgml index 11e387d..95f5bc3 100644 --- a/developers-reference.sgml +++ b/developers-reference.sgml @@ -7,7 +7,7 @@ %dynamicdata; - + @@ -969,14 +969,17 @@ which control how packages move from unstable to testing are tightened. Packages which are too buggy are removed. No changes are allowed into testing except for bug fixes. After some time has elapsed, depending on progress, the testing distribution -goes into a `deep freeze', when no changes are made to it except those -needed for the installation system. This is called a “test cycle”, -and it can last up to two weeks. There can be several test cycles, -until the distribution is prepared for release, as decided by the -release manager. At the end of the last test cycle, the -testing distribution is renamed to stable, -overriding the old stable distribution, which is removed at -that time (although it can be found at &archive-host;). +is frozen even further. +Details of the handling of the testing distribution are published +by the Release Team on debian-devel-announce. +After the open issues are solved to the satisfaction of the Release Team, +the distribution is released. +Releasing means +that testing is renamed to stable, +and a new copy is created for the new testing, +and the previous stable is renamed to oldstable +and stays there until it is finally archived. +On archiving, the contents are moved to &archive-host;).

This development cycle is based on the assumption that the unstable distribution becomes stable after passing a @@ -992,6 +995,9 @@ batch into the stable distribution and the revision level of the stable distribution is incremented (e.g., ‘3.0’ becomes ‘3.0r1’, ‘2.2r4’ becomes ‘2.2r5’, and so forth). +Please refer to +uploads to the stable distribution +for details.

Note that development under unstable continues during the freeze period, since the unstable distribution remains in -- 2.30.2