Hi. As Colin Watson has said[1]: "Over the next two or three weeks, we need to concentrate hard on stabilizing the system and fixing the 200-odd release-critical bugs that remain, either by making minimal changes to packages or by removing them." So we need to make an real effort to decrease the number of RC bugs drastically. To give the autobuilders some time to build uploaded packages we should try to fix most of the RC bug in the next week. (All others will have a good chance to be held out of testing by the freeze. Any of them will require the release team to investigate an upload to t-p-u ... ) I therefor announce the next week to be a Bug-Squashing Party. I will be in #debian-bugs both on irc.debian.org and irc.oftc.net the whole time[2] trying to keep this going and appeal to all people to participate on the BSP for one or more days and come to #debian-bugs, so we can coordinate, discuss complicated cases, and sponsor patches from non-DDs. (All other information will be available there) The week will be ended by a real life BSP in Darmstadt, Germany where I will attend, too[3]. We need to make sure that we don't make things worse by introducing wrong fixes or breaking packages. Therefor we should _not_ introduce something like a 0-day NMU policy. DELAYED/3-Day should suffice for most cases. As usual patches should be made minimal, especially so short before release! All package maintainers with RC bugs files against there packages can help the effort by clearly describing the status of their bugs in the BTS. [1] http://lists.debian.org/debian-devel-announce/2004/08/msg00003.html [2] Sadly enough I still will need some sleep, though ;) [3] http://lists.debian.org/debian-events-eu/2004/07/msg00113.html Gruesse, -- Frank Lichtenheld <djpig@debian.org> www: http://www.djpig.de/
Attachment:
pgpC8VOuddCIl.pgp
Description: PGP signature