tweaks

[wiki.git] / doc / LennyBugs

diff --git a/doc/LennyBugs b/doc/LennyBugs
index c641262b7dc788fe5b445156ae3d603f2f8d0b94..6a9d1f4eb0547b3869eafa61bd880e59756bfbb6 100644 (file)
--- a/doc/LennyBugs
+++ b/doc/LennyBugs
@@ -1,6 +1,6 @@
 = Logistics =
 
-SIPB is running a bug-squashing hackathon for release-critical bugs in Debian Lenny
+SIPB is running a bug-squashing hackathon for release-critical bugs in Debian Lenny.
 
 Place: '''W20-557''', the SIPB office[[BR]]
 Date: '''Saturday''', 2008-12-13, between end-of-classes and finals week[[BR]]
@@ -11,11 +11,14 @@ Time: starting '''2 PM''', running to about 10 PM; come for any portion
 '''Q''': What's Lenny?[[BR]]
 '''A''': Lenny is the upcoming next stable release of Debian GNU/Linux.  It was scheduled for September 2008 but has slipped to spring 2009.  The last release was Etch in spring 2007, so Debian users are eagerly awaiting a new release.
 
+'''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''': 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.
 
 '''Q''': I've never tried to hack on a Debian package.[[BR]]
-'''A''': No problem, we have three Debian Developers pledged to attend, and Debian-packaging experts from SIPB's Debathena and XVM projects.  They'll all be focussed on helping newer people find a good bug, make progress and stay unstuck on solving it, and get the fixes applied in Debian.  No Debian experience is necessary.
+'''A''': No problem, we have three Debian Developers pledged to attend, plus Debian-packaging experts from SIPB's Debathena and XVM projects.  They'll all be focussed on helping newer people find a good bug, make progress and stay unstuck on solving it, and get the fixes applied in Debian.  No Debian experience is necessary.
 
 = The Bugs =