[developers-reference] 01/05: Mention rationale for including the description in ITPs. Closes: #494332
This is an automated email from the git hooks/post-receive script.
lucas pushed a commit to branch master
in repository developers-reference.
commit 97f8e71c422c4951a94d4f10bfe2c0a3b026e078
Author: Lucas Nussbaum <lucas@debian.org>
Date: Sun Aug 24 14:34:31 2014 -0700
Mention rationale for including the description in ITPs. Closes: #494332
---
debian/changelog | 2 ++
pkgs.dbk | 5 +++--
2 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/debian/changelog b/debian/changelog
index 45b1a47..b59cd24 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -10,6 +10,8 @@ developers-reference (3.4.14) UNRELEASED; urgency=medium
* Drop section on debsums as this functionality is now integrated in
dpkg. Closes: #750990
* Mention other types of checksums besides MD5. Closes: #750994
+ * Mention rationale for including the description in ITPs. Closes:
+ #494332
-- Paul Wise <pabs@debian.org> Wed, 20 Aug 2014 18:43:04 -0700
diff --git a/pkgs.dbk b/pkgs.dbk
index ba53ef0..5a34b95 100644
--- a/pkgs.dbk
+++ b/pkgs.dbk
@@ -23,8 +23,9 @@ pages</ulink> for more information.
Assuming no one else is already working on your prospective package, you must
then submit a bug report (<xref linkend="submit-bug"/>) against the
pseudo-package <systemitem role="package">wnpp</systemitem> describing your
-plan to create a new package, including, but not limiting yourself to, a
-description of the package, the license of the prospective package, and the
+plan to create a new package, including, but not limiting yourself to, the
+description of the package (so that others can review it),
+the license of the prospective package, and the
current URL where it can be downloaded from.
</para>
<para>
--
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/collab-maint/developers-reference.git
Reply to: