tags 485837 + patch thanks Thomas Viehmann <[EMAIL PROTECTED]> writes: > Section 5.1 on New Packages currently contains the sentence > >> If you feel it's necessary, send a copy to >> [EMAIL PROTECTED] 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). > > I wonder whether it would be preferable to make using that a (strong) > recommendation along the lines of [...]
I agree with this request. Proposed diff, please review: Index: pkgs.dbk =================================================================== --- pkgs.dbk (revision 5230) +++ pkgs.dbk (working copy) @@ -28,14 +28,17 @@ 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: Marc -- BOFH #441: Hash table has woodworm
pgpTgizfnFgeU.pgp
Description: PGP signature
