RC Bug Squashing Contest
The freeze for squeeze is getting closer, and we need to fix the remaining bugs in testing/unstable real soon now!
A bug squashing party is a time to gather and work together on fixing bugs. This bug squashing party is happening during DebCamp/DebConf, and it is a contest, a way to learn and teach each other, and a party!
We will track what bugs we squash so we can get a good overall count, but also whoever squashes the most bugs will get prizes!
 Technical details
- Start: 1st day of DebCamp (2010-07-25)
- End: Saturday, 2010-08-07, 12:00 EDT (16:00 UTC)
- Awards: during the Closing Ceremony of DebConf10 (Saturday, 2010-08-07, 16:00 EDT (20:00 UTC))
- First prize: a GuruPlug, sponsored by Marvell.
- Second and third prizes: HP netbooks.
- Other prizes: books from Pearson.
Thanks to all the sponsors!
- Participants: Everybody, whether at DebCamp/DebConf or at home, whether user or maintainer or DM or DD or ...
- Judges: gregoa, mehdi
- Only one person can claim a closed RC bug.
- "Closed" in testing/unstable means
- closed by an upload; in this case the Changed-By line counts
- closed by a mail to the BTS control bot, including proper reasoning; then we have a From:
- severity downgraded, again with proper reasoning and without complaints from the maintainer/release team; again, the From: is available
- closed by a package removal
- A bug must be closed (and not only tagged pending) by the deadline on Saturday noon (relevant for uploads to the DELAYED queue).
- Duplicate/merged bugs only count as one.
- If more than one person reach the same number of closed RC bugs, the judges will throw a coin/roll a dice at the award ceremony.
Everyone can nominate themselves as soon as a bug is closed (according to the rules mentioned above).
If you close a bug, add yourself here:
 Special category "stable"
Although closing RC bugs in lenny doesn't help for the squeeze release, it's highly appreciated. We're looking into providing a special reward for the winner in this category. Please add yourself to this table:
|Gerfried Fuchs (explicit lenny RCs)||#589823 #586620 #570573 #570218 #558025 #574042 #577283 #552585 #549528 #549391 #549613 #550115 #550256 #567265 #548918 #549033 #549039 #549074 #590224 #590623 #590678 #590731 #590733 #590810 #590809 #590770 #590763 #590761 #590756 #590750 #546976 #547463 #548019 #548174 #548578 #591049 #547725 #547726 #548217 #546585 #546679 #545665 #545982 #546068 #591298 #591346 #544678 #591566 #591562 #591531 #591530 #591527 #591503 #591431 #543787 #543804 #544497 #544645 #591594 #591591 #544301 #542476 #542550 #542901 #542984 #543351 #542496 #542497 #541562 #541709 #542300 #542320 #542446 #591648 #539813 #540062 #540530||77||1|
|Ansgar Burchardt||#581194 #544894||2||2|
- I: Invalid (already fixed, fixed before the start date, ...)
- C: Confirmed
- D: Double claim
Coordination, questions, etc. happen -- as usual -- in #debian-bugs (irc.debian.org, a.k.a. OFTC)
- RC bug squashing primer - a great "classic" by Steve Langasek
- RCBW - motivations for fixing RC bugs via NMUs and let others know
- official NMU guidelines - from the Developer's Reference
There are various lightening workshops! Are you interested in doing one? They are informal, quick and easy. You dont need to be an expert at all, but willing to give an overview, and maybe guide some hands-on. So maybe a 5-10 minute talk, people try things out, and you answer questions, no pressure!
Add your ideas below, and put your name by them.
- Newb's guide to gdb (ari)
- making sure your package builds on architectures
- when packages FTBFS, where to go to buildd logs, and who to contact (taggart)
- RC bug triaging (vorlon?)
- using the BTS (don?)
- schroot/pbuilder/kvm/vserver/etc. building for particular suites
- debian version strings and you, how to make sure backports and custom versions upgrade correctly
- how to do an NMU
- how to use lintian and updating packages to new versions of Policy (Russ?)
- who to contact when you need things you can't do yourself, a flowchart (taggart, by asking the RMs,DSA,buildd admins, etc.)
NOTE: This is a tentative schedule, actually its a completely fake one
 day 1
- 19:00 - arrival
- 20:00 or 21:00 - Maybe small hints/tutorials on bug squashing best practices. Builds on previous workshops
 day 2
- 10:00 to 11:00 - Regroup, as soon as we can
- afternoon - perhaps another mini-workshop
 Things You Can Do
- Fix bugs directly, contribute a patch to the BTS.
- Perhaps a fix exists somewhere else on the internet, and you just need to test it with Debian. You don't necessarily have to figure it out yourself, work with people
- Look for bugs which are fixed in the upstream version. Note this in the BTS, see if the upgrade can be done smoothly.
- Look for bugs which are marked "unreproducible" or "needs more information". Can you provide some useful information ("works for me" can be useful, too, sometimes)
- Look for issues with upgrading packages or to squeeze.
- RC bugs that have a fix in Ubuntu (see below for a listing of packages with a newer version in Ubuntu).
- Help with documentation for squeeze.
- Look at a Team and find their list of RC bugs. This can help you target towards your specialty.
- Release-critical bugs lists:
- http://udd.debian.org/cgi-bin/rcbugs.cgi -- Top of page is bugs with a patch. Patch needs uploading by a DD, but everyone can help with testing the patches to make sure that they work properly. Bottom section is RC bugs in Debian, with a newer version in Ubuntu. The Ubuntu version may have a fix to the bug, which can be gotten and tested against the Debian package.
- Python RC bugs ; 2.6 transition ; for more see #debian-python topic
- Ruby RC bugs: or see #debian-ruby topic
- Perl RC bugs or see #debian-perl topic, DebianPerlGroup/OpenTasks
- Look at other Teams and see what interests you, find their RC bug lists and try your hand at them. The team members will likely be happy to help you get started.