(no commit message)

diff --git a/doc/LennyBugs b/doc/LennyBugs
index 8d7820a456d5942805e10ffa842026d8e0eecc95..71ab1f3bac0c268841fb2750b66bacbc7ddd90a7 100644 (file)
--- a/doc/LennyBugs
+++ b/doc/LennyBugs
@@ -17,6 +17,9 @@ Contact the SIPB Chair, Greg Price (`price@mit.edu`), or Vice-Chair, Nelson Elha
 '''Q''': What's a release-critical bug?[[BR]]
 '''A''': A '''release-critical (RC) bug''' is a Debian bug of any of the highest levels of severity.  RC bugs break a program completely, break some users' systems, or do similarly bad things.  At last count there were 109 bugs (below) affecting Lenny.  Every one of those bugs has to be dealt with one way or another before Lenny will release.
 
+'''Q''': How is this list of bugs different from [http://bugs.debian.org/release-critical/other/testing.html]?[[BR]]
+'''A''': The list on `bugs.debian.org` includes bugs which have been fixed, but haven't passed a requisite waiting period before being introduced into Lenny. Our list is only bugs for which there is no fix.
+
 '''Q''': I use '''Ubuntu'''.  Why do I care about Debian releases?[[BR]]
 '''A''': Because Lenny is in the final, "freeze", stage of the cycle, many Debian contributors are holding off new versions of the software they maintain in order to focus on stabilizing and bugfixing Lenny.  Since Ubuntu depends on Debian for >90% of its packaging work, that means less new software for Ubuntu until Lenny releases.