bugs closed in NMUs should uses 'closes' changelog entries,

closes: #133951

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

diff --git a/developers-reference.sgml b/developers-reference.sgml
index ad1efc628674067e6b2127b2539f61385c492d72..2d7a1d5cab2d3c8a379516efe6791f0241d7cea6 100644 (file)
--- a/developers-reference.sgml
+++ b/developers-reference.sgml
@@ -5,7 +5,7 @@
   <!-- common, language independant entities -->
   <!entity % commondata  SYSTEM "common.ent" > %commondata;
   <!-- CVS revision of this document -->
-  <!entity cvs-rev "$Revision: 1.76 $">
+  <!entity cvs-rev "$Revision: 1.77 $">
 
   <!-- if you are translating this document, please notate the RCS
        revision of the developers reference here -->
@@ -1521,28 +1521,27 @@ porters who have to do recompiles &mdash; chalk it up as a weakness in how
 we maintain our archive.)
          <p>
 If the source NMU (non-maintainer upload) fixes some existing bugs,
-the bugs in the Bug Tracking System which are fixed need to be
-<em>notified</em> but not actually <em>closed</em> by the
-non-maintainer.  Technically, only the official package maintainer or
-the original bug submitter are allowed to close bugs.  However, the
-person making the non-maintainer release must send a short message to
-the relevant bugs explaining that the bugs have been fixed by the NMU.
-Using <email>control@bugs.debian.org</email>, the party doing the NMU
-should also set the severity of the bugs fixed in the NMU to `fixed'.
-This ensures that everyone knows that the bug was fixed in an NMU;
-however the bug is left open until the changes in the NMU are
-incorporated officially into the package by the official package
-maintainer.  Also, open a bug with the patches needed to fix the
-problem, or make sure that one of the other (already open) bugs has
-the patches.
-         <p>
-The normal maintainer will either apply the patch or employ an
-alternate method of fixing the problem.  Sometimes bugs are fixed
-independently upstream, which is another good reason to back out an
-NMU's patch.  If the maintainer decides not to apply the NMU's patch
-but to release a new version, the maintainer needs to ensure that the
-new upstream version really fixes each problem that was fixed in the
-non-maintainer release.
+these bugs should be tagged <em>fixed</em> in the Bug Tracking
+System rather than closed.  By convention, only the official package
+maintainer or the original bug submitter are allowed to close bugs.
+Fortunately, Debian's archive system recognizes NMUs and thus marks
+the bugs fixed in the NMU appropriately if the person doing the NMU
+has listed all bugs in the changelog with the <tt>Closes:
+bug#<var>nnnnn</var></tt> syntax (see <ref id="upload-bugfix"> for
+more information describing how to close bugs via the changelog).
+Tagging the bugs <em>fixed</em> ensures that everyone knows that the
+bug was fixed in an NMU; however the bug is left open until the
+changes in the NMU are incorporated officially into the package by
+the official package maintainer.
+         <p>
+Also, after doing an NMU, you have to open a new bug and include a
+patch showing all the changes you have made.  The normal maintainer
+will either apply the patch or employ an alternate method of fixing
+the problem.  Sometimes bugs are fixed independently upstream, which
+is another good reason to back out an NMU's patch.  If the maintainer
+decides not to apply the NMU's patch but to release a new version,
+the maintainer needs to ensure that the new upstream version really
+fixes each problem that was fixed in the non-maintainer release.
          <p>
 In addition, the normal maintainer should <em>always</em> retain the
 entry in the changelog file documenting the non-maintainer upload.