Secs "Uploads to {stable,testing-proposed-updates}" retitled to make

 it clear these are special cases

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

diff --git a/developers-reference.sgml b/developers-reference.sgml
index 53e34a1b3b6de72be077f7c80c1a35be4901128f..a86386ec698e921b12591d62fe783296e22639e7 100644 (file)
--- a/developers-reference.sgml
+++ b/developers-reference.sgml
@@ -6,7 +6,7 @@
   <!entity % commondata  SYSTEM "common.ent" > %commondata;
 
   <!-- CVS revision of this document -->
-  <!entity cvs-rev "$Revision: 1.204 $">
+  <!entity cvs-rev "$Revision: 1.205 $">
   <!-- if you are translating this document, please notate the CVS
        revision of the developers reference here -->
   <!--
@@ -1664,7 +1664,8 @@ because the dependencies of the package may vary with the distribution.
 In particular, it never makes sense to combine the <em>experimental</em>
 distribution with anything else (see <ref id="experimental">).
 
-       <sect1 id="upload-stable">Uploads to <em>stable</em>
+       <sect1 id="upload-stable">
+          <heading>Special case: uploads to the <em>stable</em> distribution</heading>
          <p>
 Uploading to <em>stable</em> means that the package will be placed into the
 <file>stable-proposed-updates</file> directory of the Debian archive for further
@@ -1703,7 +1704,8 @@ verbose, if necessary) in your changelog entries for uploads to
 <em>stable</em>, because otherwise the package won't be considered for
 inclusion.
 
-       <sect1 id="upload-t-p-u">Uploads to <em>testing-proposed-updates</em>
+       <sect1 id="upload-t-p-u">
+          <heading>Special case: uploads to <em>testing-proposed-updates</em></heading>
          <p>
 The testing distribution is fed with packages from unstable according to the rules
 explained in <ref id="testing">. However, the release manager may stop the testing