X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=developers-reference.git;a=blobdiff_plain;f=pkgs.dbk;h=93a8871e22292739e953d06fb819d7c3c26d0920;hp=873c42c4e7d0678c609153727434f581e58401f8;hb=20c465fe39765b29c63e427c8a7ee6350e1d66d1;hpb=52dc65cfa7d8ecbd0c6631fa9ca9c61be60be0a6

diff --git a/pkgs.dbk b/pkgs.dbk
index 873c42c..93a8871 100644
--- a/pkgs.dbk
+++ b/pkgs.dbk
@@ -1975,8 +1975,20 @@ Before doing an NMU, consider the following questions:
 <itemizedlist>
 <listitem>
 <para>
-Does your NMU really fix bugs? Fixing cosmetic issues or changing the
-packaging style in NMUs is discouraged.
+Have you geared the NMU towards helping the maintainer? As there might
+be disagreement on the notion of whether the maintainer actually needs
+help on not, the DELAYED queue exists to give time to the maintainer to
+react and has the beneficial side-effect of allowing for independent
+reviews of the NMU diff.
+</para>
+</listitem>
+<listitem>
+<para>
+Does your NMU really fix bugs? ("Bugs" means any kind of bugs, e.g.
+wishlist bugs for packaging a new upstream version, but care should be
+taken to minimize the impact to the maintainer.) Fixing cosmetic issues
+or changing the packaging style (e.g. switching from cdbs to dh) in NMUs
+is discouraged.
 </para>
 </listitem>
 <listitem>
@@ -2059,7 +2071,7 @@ Other NMUs: 10 days
 
 <para>
 Those delays are only examples. In some cases, such as uploads fixing security
-issues, or fixes for trivial bugs that blocking a transition, it is desirable
+issues, or fixes for trivial bugs that block a transition, it is desirable
 that the fixed package reaches <literal>unstable</literal> sooner.
 </para>