NMUs: Remove the paragraphs asking `did you give the maintainer enough time' and...

diff --git a/debian/changelog b/debian/changelog
index 840f8a4a67642cef798df5d44310a8233727fc04..aebadfd5f7a809aa46d8a67b9f44a0c7ace4d40c 100644 (file)
--- a/debian/changelog
+++ b/debian/changelog
@@ -9,6 +9,11 @@ developers-reference (3.4.14~~iwj) UNRELEASED; urgency=low
     to go against the wishes of the maintainer.
   * NMUs: Remove the mention of DELAYED in the first bullet point; this is
     dealt with better and at greater length later on.
+  * NMUs: Remove the paragraphs asking `did you give the maintainer enough
+    time' and `did you contact the maintainer' (with are also pretty much
+    duplicates of each other).  The effect is that people are no longer
+    discouraged by dev ref from NMUing directly to DELAYED-10 even if the
+    bug has only just been discovered.
 
  --
 

diff --git a/pkgs.dbk b/pkgs.dbk
index 197f4b03e1029030c2c43a4d23a9ecf175c35fe3..76ad7d33c9aadfad6b810eee688971433b24fd8f 100644 (file)
--- a/pkgs.dbk
+++ b/pkgs.dbk
@@ -2002,13 +2002,6 @@ uploaded to substantially DELAYED queues.
 </listitem>
 <listitem>
 <para>
-Did you give enough time to the maintainer? When was the bug reported to the
-BTS? Being busy for a week or two isn't unusual.  Is the bug so severe that it
-needs to be fixed right now, or can it wait a few more days?
-</para>
-</listitem>
-<listitem>
-<para>
 How confident are you about your changes? Please remember the Hippocratic Oath:
 "Above all, do no harm." It is better to leave a package with an open grave bug
 than applying a non-functional patch, or one that hides the bug instead of
@@ -2019,11 +2012,6 @@ many people will be very unhappy about it.
 </listitem>
 <listitem>
 <para>
-Have you clearly expressed your intention to NMU, at least in the BTS?
-It is also a good idea to try to contact the
-maintainer by other means (private email, IRC).
-</para>
-</listitem>
 <listitem>
 <para>
 If the maintainer is usually active and responsive, have you tried to contact