- 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
- 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
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
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
<!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 -->
<!--
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:
<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 <jbuzz@debian.org>, Adam Rex <arex@debian.org>
+</example>
+</p>
</item>
<item>
<p>
<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
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>