- Added a section about "Bug Squashing Parties".

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

diff --git a/debian/changelog b/debian/changelog
index 5c656b96fd654a9fb83487c88f3fcbbed39da395..cae8435637c41bc11ea7e892c65e996852cdebf9 100644 (file)
--- a/debian/changelog
+++ b/debian/changelog
@@ -10,7 +10,7 @@ developers-reference (3.1) unstable; urgency=low
     - Applied the patch of Matt Zimmerman. Thanks Matt ! closes: #145287
     - Added the explanation about how to replace an .orig.tar.gz.
       closes: #150392
-    - Mostly deleted the paragraph about security upload in the 
+    - Mostly deleted the paragraph about security upload in the
       section explaining source NMU. Just added a link to point to
       "Handling security-related bugs". closes: #159935
     - Added a link to the Technical Committee web page (in the "Bug
@@ -18,7 +18,7 @@ developers-reference (3.1) unstable; urgency=low
     - Explain uploads to testing-proposed-updates, mentions briefly
       stable-security and testing-security. closes: #149666
       Removed the comment about uploads to frozen.
-    - Documented the "Developer's packages overview" web portal. 
+    - Documented the "Developer's packages overview" web portal.
       closes: #158650
     - Added a reference to debian-l10n-english in "Writing useful
       descriptions". closes: #158609
@@ -26,6 +26,7 @@ developers-reference (3.1) unstable; urgency=low
       autoconf/automake". closes: #158045
     - Documented associated features to db.debian.org like SSH key
       replication and *.debian.net DNS entry. closes: #155389
+    - Added a section about "Bug Squashing Parties".
   * Josip Rodin:
     - removed obsolete, needless dupload variables
     - applied linguistic fixes from David Kimdon, closes: #150572
@@ -34,7 +35,7 @@ developers-reference (3.1) unstable; urgency=low
       mostly rewrote it to exclude real machine names and be better organized
     - updated the mailing lists section
 
- -- Raphael Hertzog <hertzog@debian.org>  Wed,  7 Aug 2002 12:51:44 +0200
+ -- Raphael Hertzog <hertzog@debian.org>  Mon,  9 Sep 2002 11:14:43 +0200
 
 developers-reference (3.0) unstable; urgency=low
 

diff --git a/developers-reference.sgml b/developers-reference.sgml
index 26f9f3450540646aa1a48e6a11520b80a9a72d55..7bc7c88245ff24f30457cc2628df6bf658d4c899 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.128 $">
+  <!entity cvs-rev "$Revision: 1.129 $">
   <!-- if you are translating this document, please notate the CVS
        revision of the developers reference here -->
   <!--
@@ -1853,7 +1853,8 @@ serious or higher severity bugs are encouraged and accepted.  Even
 during this window, however, you should endeavor to reach the current
 maintainer of the package; they might be just about to upload a fix
 for the problem.  As with any source NMU, the guidelines found in <ref
-id="nmu-guidelines"> need to be followed.
+id="nmu-guidelines"> need to be followed. Special exceptions are made
+for <ref id="qa-bsp">.
        <p>
 Uploading bug fixes to unstable by non-maintainers should only be done
 by following this protocol:
@@ -2303,7 +2304,11 @@ version control system, such as <prgn>CVS</prgn> or
               <p>
 Add the co-maintainer's correct maintainer name and address to the
 <tt>Uploaders</tt> field in the global part of the
-<file>debian/control</file> file.</p>
+<file>debian/control</file> file.
+<example>
+Uploaders: John Buzz &lt;jbuzz@debian.org&gt;, Adam Rex &lt;arex@debian.org&gt;
+</example>
+</p>
             </item>
             <item>
               <p>
@@ -3140,6 +3145,8 @@ list.
 
 
       <sect id="qa-effort">Quality Assurance effort
+       
+       <sect1 id="qa-daily-work">Daily work
        <p>
 Even though there is a dedicated group of people for Quality
 Assurance, QA duties are not reserved solely for them. You can
@@ -3149,7 +3156,33 @@ possible. If you do not find that possible, then you should consider
 orphaning some of your packages (see <ref
 id="orphaning">). Alternatively, you may ask the help of other people
 in order to catch up the backlog of bugs that you have (you can ask
-for help on &email-debian-qa; or &email-debian-devel;).
+for help on &email-debian-qa; or &email-debian-devel;). At the same
+time, you can look for co-maintainers (see <ref id="collaborative-maint">).
+       
+       <sect1 id="qa-bsp">Bug Squashing Parties
+       <p>
+From time to time the QA group organizes bug squashing parties to get rid of
+as many problems as possible. They are announced on &email-debian-devel-announce;
+and the announce explains what area will be focused on during the party:
+usually they focus on release critical bugs but it may happen that they
+decide to help finish a major upgrade going on (like a new perl version
+which requires recompilation of all the binary modules).
+       <p>
+The rules for non-maintainer uploads differ during the parties because
+the announce of the party is considered like a prior notice for NMU. If
+you have packages that may be affected by the party (because they have
+release critical bugs for example), you should send an update to each of
+the corresponding bug to explain their current status and what you expect
+from the party. If you don't want an NMU, or if you're only interested in a
+patch, or if you will deal yourself with the bug, please explain that in
+the BTS.
+       <p>
+People participating in the party have special rules for NMU, they can
+NMU withour prior notice if they upload their NMU to
+DELAYED/3-day at least. All other NMU rules applies as usually, they
+should send the patch of the NMU in the BTS (in one of the open bugs
+fixed by the NMU or in a new bug tagged fixed). They should
+also respect the maintainer's wishes if he expressed some. 
 
     <sect id="mia-qa">Dealing with unreachable maintainers
       <p>