X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=pkgs.dbk;h=8f1f36b9cd1928e497af1ffbc5e1afcd372d2d29;hb=e81cdebedab690ef881d87af6f533e51c026565c;hp=1e0b29d9593b81ade4d436d9ef8540f87a748780;hpb=933cc23b634dc089f3ee6dfde76b4b6bf432be7d;p=developers-reference.git
diff --git a/pkgs.dbk b/pkgs.dbk
index 1e0b29d..8f1f36b 100644
--- 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.
-You should set the subject of the bug to ``ITP: foo
--- short description'', substituting the name of the
-new package for foo. The severity of the bug report
-must be set to wishlist. If you feel it's necessary, send
-a copy to &email-debian-devel; by putting the address in the
-X-Debbugs-CC: header of the message (no, don't use
-CC:, because that way the message's subject won't indicate
-the bug number).
+You should set the subject of the bug to ITP:
+foo -- short
+description, substituting the name of the new
+package for foo.
+The severity of the bug report must be set to wishlist.
+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.
Please include a Closes:
@@ -735,9 +739,9 @@ several developers working on the same package.
-Once a corrected package is available in the unstable
-distribution, you can close the bug. This can be done automatically, read
- .
+Once a corrected package is available in the archive, the bug should be
+closed indicating the version in which it was fixed. This can be done
+automatically, read .
@@ -2281,7 +2285,7 @@ available in unstable, but not affecting the version in
It must be available on all architectures on which it has previously been built
-in unstable. may be of interest
+in unstable. may be of interest
to check that information;