Clarify ITP instructions and emphasize our wish that people send

ITPs, explaining a few of the reasons. Thanks for the note,
Thomas. Closes: #485837

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

diff --git a/debian/changelog b/debian/changelog
index ec4155831ae904d64a9eda06a80f3f21ab2e343a..1e49c49f44cdccc7b6ed6dc0e504d989876dd861 100644 (file)
--- a/debian/changelog
+++ b/debian/changelog
@@ -46,6 +46,9 @@ developers-reference (3.4.0) UNRELEASED; urgency=low
   * Update explanation of best practice for closing bugs, seems to
     have been forgotten when everything was upgraded to use
     debbugs version-tracking. Closes: #485969
+  * Clarify ITP instructions and emphasize our wish that people send
+    ITPs, explaining a few of the reasons. Thanks for the note,
+    Thomas. Closes: #485837
 
  -- Marc 'HE' Brockschmidt <he@debian.org>  Sun, 01 Jun 2008 16:26:33 +0200
 

diff --git a/pkgs.dbk b/pkgs.dbk
index d96c0ae8ac6c88d7ee3e124928c656ff5b4cc72a..6e7413ef7c9d8cc83c6e681925d63320b4ed417e 100644 (file)
--- a/pkgs.dbk
+++ b/pkgs.dbk
@@ -28,14 +28,18 @@ description of the package, the license of the prospective package, and the
 current URL where it can be downloaded from.
 </para>
 <para>
-You should set the subject of the bug to ``ITP: <replaceable>foo</replaceable>
--- <replaceable>short description</replaceable>'', substituting the name of the
-new package for <replaceable>foo</replaceable>.  The severity of the bug report
-must be set to <literal>wishlist</literal>.  If you feel it's necessary, send
-a copy to &email-debian-devel; by putting the address in the
-<literal>X-Debbugs-CC:</literal> header of the message (no, don't use
-<literal>CC:</literal>, because that way the message's subject won't indicate
-the bug number).
+You should set the subject of the bug to <literal>ITP: 
+<replaceable>foo</replaceable> -- <replaceable>short
+description</replaceable><literal>, substituting the name of the new
+package for <replaceable>foo</replaceable>. 
+The severity of the bug report must be set to <literal>wishlist</literal>.
+Please send a copy to &email-debian-devel; by using the X-Debbugs-CC
+header (don't use CC:, because that way the message's subject won't
+indicate the bug number). If you are packaging so many new packages (>10)
+that notifying the mailing list in seperate messages is too disruptive,
+do send a summary after filing the bugs to the debian-devel list instead.
+This will inform the other developers about upcoming packages and will
+allow a review of your description and package name.
 </para>
 <para>
 Please include a <literal>Closes: