From eb78146c1cb9e948d354d98de029f975bbcccd0e Mon Sep 17 00:00:00 2001 From: he Date: Fri, 13 Jun 2008 07:41:51 +0000 Subject: [PATCH] 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 --- debian/changelog | 3 +++ pkgs.dbk | 20 ++++++++++++-------- 2 files changed, 15 insertions(+), 8 deletions(-) diff --git a/debian/changelog b/debian/changelog index ec41558..1e49c49 100644 --- 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 Sun, 01 Jun 2008 16:26:33 +0200 diff --git a/pkgs.dbk b/pkgs.dbk index d96c0ae..6e7413e 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: -- 2.30.2