Use po4a --previous option (store previous string version in the po)

[developers-reference.git] / developer-duties.dbk

diff --git a/developer-duties.dbk b/developer-duties.dbk
index 2e501f3069cf876bdabd480c891b0531dedc99c9..b2d375fd00bd676f7a3b8093ee7794cbb6cb4145 100644 (file)
--- a/developer-duties.dbk
+++ b/developer-duties.dbk
@@ -152,6 +152,12 @@ can be included there, so that you won't have to modify the sources of the next
 upstream version.  Whatever changes you need, always try not to fork from the
 upstream sources.
 </para>
+<para>
+If you find that the upstream developers are or become hostile towards Debian
+or the free software community, you may want to re-consider the need to
+include the software in Debian. Sometimes the social cost to the
+Debian community is not worth the benefits the software may bring.
+</para>
 </section>
 
 <section id="rc-bugs">
@@ -160,8 +166,8 @@ upstream sources.
 Generally you should deal with bug reports on your packages as described in
 <xref linkend="bug-handling"/> .  However, there's a special category of bugs
 that you need to take care of — the so-called release-critical bugs (RC
-bugs).  All bug reports that have severity <emphasis>critical</emphasis>,
-<emphasis>grave</emphasis> or <emphasis>serious</emphasis> are considered to
+bugs).  All bug reports that have severity <literal>critical</literal>,
+<literal>grave</literal> or <literal>serious</literal> are considered to
 have an impact on whether the package can be released in the next stable
 release of Debian.  These bugs can delay the Debian release and/or can justify
 the removal of a package at freeze time.  That's why these bugs need to be