From: Greg Price Date: Thu, 11 Dec 2008 04:11:47 +0000 (-0500) Subject: tweaks X-Git-Tag: trac~161 X-Git-Url: https://sipb.mit.edu/gitweb.cgi/wiki.git/commitdiff_plain/8ddeb9177ecb92372fe2ea741bf0b7731cfcc793?ds=sidebyside tweaks --- diff --git a/doc/LennyBugs b/doc/LennyBugs index d139986..c641262 100644 --- a/doc/LennyBugs +++ b/doc/LennyBugs @@ -3,7 +3,7 @@ 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 classes and finals[[BR]] +Date: '''Saturday''', 2008-12-13, between end-of-classes and finals week[[BR]] Time: starting '''2 PM''', running to about 10 PM; come for any portion = FAQ = @@ -12,7 +12,7 @@ Time: starting '''2 PM''', running to about 10 PM; come for any portion '''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''': 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. +'''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.