updated the FAQ using info from the mentioned debian-devel thread and elsewhere

CVS version numbers

english/devel/testing.wml: 1.5 -> 1.6

1 files changed, 21 insertions, 1 deletions

diff --git a/english/devel/testing.wml b/english/devel/testing.wml
index 83da39fce8e..b25c7b1bea8 100644
--- a/english/devel/testing.wml
+++ b/english/devel/testing.wml
@@ -1,4 +1,5 @@
 #use wml::debian::template title="Debian ``testing'' distribution" BARETITLE=true
+#include "$(ENGLISHDIR)/releases/info"
 
 <p>For basic, user-oriented information about the testing distribution,
 please see <a href="$(DOC)/FAQ/ch-ftparchives#s-testing">the Debian FAQ</a>.</p>
@@ -23,7 +24,8 @@ satisfies all of the following criteria:</p>
   corresponding version in "testing" was compiled on;</li>
 
   <li>It must have fewer release-critical bugs than, or the same number as,
-  the version currently in "testing";</li>
+  the version currently in "testing" (<a href="#faq">see below</a> for
+  more information);</li>
 
   <li>All of its dependencies must <em>either</em> be satisfiable by
   packages already in "testing", <em>or</em> be satisfiable by the group
@@ -53,6 +55,24 @@ satisfies all of the following criteria:</p>
 
 <h2><a name="faq">Frequently Asked/Answered Questions</a></h2>
 
+<h3><q>What are release-critical bugs, and how do they get counted?</q></h3>
+
+<p>All bugs of some higher severities are by default considered
+<em><a href="http://bugs.debian.org/release-critical/">release-critical</a></em>;
+currently, these are <strong>critical</strong>, <strong>grave</strong> and
+<strong>serious</strong> bugs.</p>
+
+<p>Such bugs are presumed to have an impact on the chances that the package
+will be released with the stable release of Debian: in general, if a package
+has open release-critical bugs filed on it, it won't get into "testing", and
+consequently won't be released in "stable".</p>
+
+<p>The "testing" bug count for a package is considered to be roughly the bug
+count at the last point when the "testing" version equalled the "unstable"
+version. The bugs tagged <strong><current_release_name></strong> or
+<strong><current_testing_name></strong> will not be counted. Bugs with the
+<strong>sid</strong> tag will be counted, though.</p>
+
 <h3><q>How could installing a package into "testing" possibly break other
 packages?</q></h3>