Hi.
Due to numerous transitions, many new upstream versions and
rapid development of native packages we had a big jump in the
numbers of RC bugs since the sarge release. To not causing a
delay down the road when we try to stabilise for the next release
we need to work on them ASAP. In the past weeks I refrained from
trying to coordinate these efforts due to Debconf and the
unavailability of ftp-master.d.o. But there are no real excuses
left.
Therefor I announce the first post-sarge Bug Squashing Party (BSP)
for the next weekend, August 5th until August 7th. Coordination
will happen over IRC channel #debian-bugs on irc.debian.org as
usual.
Unlike shortly before sarge release there should be plenty of bugs
for all levels of complexity, programming language skills and
time requirements. So if you never attended to a BSP before and
want to help, _now_ is the right time to start. The RC Bug Squashing
HOWTO[0] by Steve Langasek gives a good introduction and is probably
a must-read for beginners. But don't hesitate to ask questions in
#debian-bugs, we will be eager to get you to do some work :)
Sponsoring of uploads should be no problem, the fastest way is
probably to send the complete NMU patch to the BTS, making the
full source package available for download somewhere, and then
asking for sponsoring on #debian-bugs.
See also the end of this mail for a list of useful links.
[0] http://people.debian.org/~vorlon/rc-bugsquashing.html
Procedures:
During the BSP we should use a 0-Day NMU policy again, that means
uploads that fix RC bugs that are more than a week old can be uploaded
directly. This worked reasonably well during the sarge release process
so I see no reason not to use it again. If you feel unsure about a
patch and/or if the patch is rather invasive, please consider asking
on #debian-bugs for review and/or giving the maintainer some time
to react by uploading to the DELAYED queue[1].
[1] http://lists.debian.org/debian-devel/2004/02/msg00887.html
and http://people.debian.org/~djpig/delayed.html
Everyone should consider reading the two announcements by Matthias
Klose and Steve Langasek about the C++ transition ([2],[3]) and
the mails by Colin Watson and Pascal Hakim about the latest BTS
features ([4],[5]) before attending the BSP.
[2] http://lists.debian.org/debian-devel-announce/2005/07/msg00001.html
[3] http://lists.debian.org/debian-devel-announce/2005/07/msg00007.html
[4] http://lists.debian.org/debian-devel-announce/2005/07/msg00010.html
[5] http://lists.debian.org/debian-devel-announce/2005/07/msg00014.html
Other useful links:
(taken from http://people.debian.org/~vorlon/rc-bugsquashing-urls.txt)
where to find available RC bugs:
http://bts.turmzimmer.net/details.php?ignore=sid&ignnew=on&new=7
build logs for failed builds:
http://buildd.debian.org/
Explanations for missing binaries:
http://people.debian.org/~igloo/status.php
List of open RC bugs for a given source package:
http://bugs.debian.org/src:<sourcepackagename>
Information on opening new bug reports:
http://bugs.debian.org/
Debian Policy:
http://www.debian.org/doc/debian-policy/
Gruesse,
--
Frank Lichtenheld <djpig@debian.org>
www: http://www.djpig.de/
Attachment:
signature.asc
Description: Digital signature