Update the instructions for uploads to the (old)stable

distributions. Emphasize the importance of contacting the SRM
team before upload. Closes: #459343

git-svn-id: svn://anonscm.debian.org/ddp/manuals/trunk/developers-reference@5219 313b444b-1b9f-4f58-a734-7bb04f332e8d

diff --git a/debian/changelog b/debian/changelog
index a3e0224cf96ed218c674ff5c4778850f8f04ae85..305102e5f57797027f5f939f3f913b923ad9aa0c 100644 (file)
--- a/debian/changelog
+++ b/debian/changelog
@@ -27,6 +27,9 @@ developers-reference (3.4.0) UNRELEASED; urgency=low
     the dev-ref up to the state of porting in the year 2008. Also
     fixes several wording issues, such as possible misunderstandings
     about the need to rebuild uploads. Closes: #483226
+  * Update the instructions for uploads to the (old)stable 
+    distributions. Emphasize the importance of contacting the SRM
+    team before upload. Closes: #459343
 
  -- Marc 'HE' Brockschmidt <he@debian.org>  Sun, 01 Jun 2008 16:26:33 +0200
 

diff --git a/pkgs.dbk b/pkgs.dbk
index db52c3d6bb05241f377d4e4e53c8706fcaa02f55..3a2813b1ac580331444101bed94de0d7a0afb2d3 100644 (file)
--- a/pkgs.dbk
+++ b/pkgs.dbk
@@ -284,16 +284,25 @@ It is not possible to upload a package into several distributions at the same
 time.
 </para>
 <section id="upload-stable">
-<title>Special case: uploads to the <literal>stable</literal> distribution</title>
+<title>Special case: uploads to the <literal>stable</literal> and 
+<literal>oldstable</literal> distributions</title>
 <para>
 Uploading to <literal>stable</literal> means that the package will transfered
-to the <literal>proposed-updates-new</literal>-queue for review by the stable
+to the <literal>proposed-updates-new</literal> queue for review by the stable
 release managers, and if approved will be installed in
 <filename>stable-proposed-updates</filename> directory of the Debian archive.
 From there, it will be included in <literal>stable</literal> with the next
 point release.
 </para>
 <para>
+To ensure that your upload will be accepted, you should discuss the changes
+with the stable release team before you upload. For that, send a mail to
+the &email-debian-release; mailing list, including the patch you want to
+apply to the package version currently in <literal>stable</literal>. Always
+be verbose and detailed in your changelog entries for uploads to the
+<literal>stable</literal> distribution.
+</para>
+<para>
 Extra care should be taken when uploading to <literal>stable</literal>.
 Basically, a package should only be uploaded to <literal>stable</literal> if
 one of the following happens:
@@ -321,7 +330,10 @@ security problems as well.  However, this practice is deprecated, as uploads
 used for Debian security advisories are automatically copied to the appropriate
 <filename>proposed-updates</filename> archive when the advisory is released.
 See <xref linkend="bug-security"/> for detailed information on handling
-security problems.
+security problems. If the security teams deems the problem to be too
+benign to be fixed through a <literal>DSA</literal>, the stable release
+managers are usually willing to include your fix nonetheless in a regular
+upload to <literal>stable</literal>.
 </para>
 <para>
 Changing anything else in the package that isn't important is discouraged,
@@ -338,19 +350,9 @@ rejected.  Making changes to dependencies of other packages (by messing with
 making those other packages uninstallable, is strongly discouraged.
 </para>
 <para>
-The Release Team (which can be reached at
-&email-debian-release;) will regularly evaluate the uploads to
-<literal>stable-proposed-updates</literal> and decide if your package can be
-included in <literal>stable</literal>.  Please be clear (and verbose, if
-necessary) in your changelog entries for uploads to
-<literal>stable</literal>, because otherwise the package won't be considered
-for inclusion.
-</para>
-<para>
-It's best practice to speak with the stable release manager
-<emphasis>before</emphasis> uploading to
-<literal>stable</literal>/<literal>stable-proposed-updates</literal>, so
-that the uploaded package fits the needs of the next point release.
+Uploads to the <literal>oldstable</literal> distributions are possible as
+long as it hasn't been archived. The same rules as for <literal>stable
+</literal> apply.
 </para>
 </section>