improved the general bugs section

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

diff --git a/developers-reference.sgml b/developers-reference.sgml
index fec32b9fc67e980fdbc8e64bd35d08c58fd71a5e..9fc6275d69691e3bdc351eba3d1c1596a224865c 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.194 $">
+  <!entity cvs-rev "$Revision: 1.195 $">
   <!-- if you are translating this document, please notate the CVS
        revision of the developers reference here -->
   <!--
@@ -1839,13 +1839,24 @@ according to their licensing, e.g. <em>main</em>, <em>contrib</em> and
 <em>non-free</em>. This is described in another section, <ref id="archive">.
 
 
-    <sect id="bug-handling">Handling package bugs
+    <sect id="bug-handling">Handling bugs
        <p>
-Often as a package maintainer, you find bugs in other packages or else
-have bugs reported to your packages which need to be reassigned.  The
-<url id="&url-bts-control;" name="BTS instructions"> can tell you how
-to do this.  Some information on filing bugs can be found in <ref
-id="submit-bug">.
+Every developer has to be able to work with the Debian <url name="bug
+tracking system" id="&url-bts;">. This includes knowing how to file bug
+reports properly, how to update them and reorder them, and how to
+process and close them. Some information on filing bugs can be found in
+<ref id="submit-bug">.
+       <p>
+The bug tracking system's features interesting to developers are described
+in the <url id="&url-bts-devel;" name="BTS documentation for developers">.
+This includes closing bugs, sending followup messages, assigning severities,
+tags, marking bugs as forwarded and other issues.
+       <p>
+Operations such as reassigning bugs to other packages, merging separate
+bug reports about the same issue, or reopening bugs when they are
+prematurely closed, are handled using the so-called control mail server.
+All of the commands available in this server are described in the
+<url id="&url-bts-control;" name="BTS control server documentation">.
 
       <sect1 id="bug-monitoring">Monitoring bugs
        <p>