Bug#494332: developers-reference: mention explicitely that ITPs must be Cced to -devel@, and why.
On 11/08/08 at 10:19 -0300, Lucas Nussbaum wrote: On 11/08/08 at 09:24 +0200, Marc 'HE' Brockschmidt wrote: Lucas Nussbaum lu...@lucas-nussbaum.net writes: Package: developers-reference Mentioned on -devel@: [...] Where's that written? I don't mean to be objectionable, but no such requirement is listed in the developer's reference: http://www.debian.org/doc/developers-reference/pkgs.html#newpackage I think it's more important to submit an ITP early to avoid duplicate work than to spend more time perfecting the package description. Ehm: | 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 debian-de...@lists.debian.org 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. I think this bug should be closed again. No, I think that we should just add something like: It is important that, in the ITP, you provide the description that you are going to use in the package. That way, other debian-devel@ readers can review it and suggest improvements. Actually, I agree that it's already in dev-ref. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#494332: developers-reference: mention explicitely that ITPs must be Cced to -devel@, and why.
Lucas Nussbaum [EMAIL PROTECTED] writes: Package: developers-reference Mentioned on -devel@: [...] Where's that written? I don't mean to be objectionable, but no such requirement is listed in the developer's reference: http://www.debian.org/doc/developers-reference/pkgs.html#newpackage I think it's more important to submit an ITP early to avoid duplicate work than to spend more time perfecting the package description. Ehm: | 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 PROTECTED] 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. I think this bug should be closed again. Marc -- BOFH #149: Dew on the telephone lines. pgp5832H32vqG.pgp Description: PGP signature
Bug#494332: developers-reference: mention explicitely that ITPs must be Cced to -devel@, and why.
On 11/08/08 at 09:24 +0200, Marc 'HE' Brockschmidt wrote: Lucas Nussbaum [EMAIL PROTECTED] writes: Package: developers-reference Mentioned on -devel@: [...] Where's that written? I don't mean to be objectionable, but no such requirement is listed in the developer's reference: http://www.debian.org/doc/developers-reference/pkgs.html#newpackage I think it's more important to submit an ITP early to avoid duplicate work than to spend more time perfecting the package description. Ehm: | 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 PROTECTED] 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. I think this bug should be closed again. No, I think that we should just add something like: It is important that, in the ITP, you provide the description that you are going to use in the package. That way, other debian-devel@ readers can review it and suggest improvements. -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | signature.asc Description: Digital signature
Bug#494332: developers-reference: mention explicitely that ITPs must be Cced to -devel@, and why.
Package: developers-reference Mentioned on -devel@: On 30/07/08 at 15:10 +1000, Hamish Moffatt wrote: On Wed, Jul 30, 2008 at 10:33:39AM +1000, Ben Finney wrote: Giuseppe Iuculano [EMAIL PROTECTED] writes: Guus Sliepen ha scritto: On Tue, Jul 29, 2008 at 11:27:55PM +0200, Giuseppe Iuculano wrote: Description : arp handler inspection That is not a short description, that is just the expansion of the acronym. Yes, this won't to be package synopsis. Then you've submitted the ITP report incorrectly. That field should be the intended 'Description' field of the package. Where's that written? I don't mean to be objectionable, but no such requirement is listed in the developer's reference: http://www.debian.org/doc/developers-reference/pkgs.html#newpackage I think it's more important to submit an ITP early to avoid duplicate work than to spend more time perfecting the package description. -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
