Fri, 09 Dec 2011
The bug webinterface of the Ultimate Debian Database currently knows about the following release critical bugs:
|Remaining to be fixed in Wheezy:||849|
Of these 849 bugs, the following tags are set:
|Pending in Wheezy:||53|
|Patched in Wheezy:||157|
|Duplicates in Wheezy:||50|
|Can be fixed in a security Update:||31|
|Contrib or non-free in Wheezy:||9|
|Claimed in Wheezy:||0|
|Delayed in Wheezy:||9|
|Otherwise fixed in Wheezy:||67|
Ignoring all the above (multiple tags possible) 551
bugs need to be fixed by Debian Contributors to get Debian 7.0
However, with the view of the Release Managers, 906 need to be dealt with for the release to happen.
Gregor Herrmann kindly posted his usual workflow for
preparing non maintainer uploads (NMUs) fixing Release Critical bugs.
I'd like to add, that it is usually a very good idea to also
pts-subscribe to the package you uploaded, just in case you
introduce some new bugs (see for #651452 or #651112 for examples of bugs I got
to know after uploading NMUs).
When subscribing you'll get copies of BTS activity, teesting migration and similar. You can either subscribe to that via the package tracking system at http://packages.qa.debian.org/<packagename> (see for example the iftop PTS) in the lower left box, or via the pts-subscribe command in the devscripts package.
I prefer the later method, as that also creates a pts-unsubscribe job via at. But please know, that you need a working mail transfer agent as well as the tool at for that. Well, and it helps if you have a machine running most of the time ;)