Fri, 30 Dec 2011
Release Critical Bug report for Week 52
The bug webinterface of the Ultimate Debian Database currently knows about the following release critical bugs:
In Total: | 1586 |
---|---|
Affecting Wheezy: | 960 |
Wheezy only: | 163 |
Remaining to be fixed in Wheezy: | 797 |
Of these 797 bugs, the following tags are set:
Pending in Wheezy: | 49 |
---|---|
Patched in Wheezy: | 117 |
Duplicates in Wheezy: | 50 |
Can be fixed in a security Update: | 26 |
Contrib or non-free in Wheezy: | 9 |
Claimed in Wheezy: | 0 |
Delayed in Wheezy: | 8 |
Otherwise fixed in Wheezy: | 49 |
Ignoring all the above (multiple tags possible) 552
bugs need to be fixed by Debian Contributors to get Debian 7.0 Wheezy
released.
However, with the view of the Release Managers, 862 need to be dealt with for the release to happen.
Please see Interpreting the
release critical bug statistics
for an explanation of the different numbers.
postet at 13:02 into [Debian/rc-stats/7.0-wheezy] permanent link
Fri, 16 Dec 2011
Release Critical Bug report for Week 50
The bug webinterface of the Ultimate Debian Database currently knows about the following release critical bugs:
In Total: | 1680 |
---|---|
Affecting Wheezy: | 1038 |
Wheezy only: | 139 |
Remaining to be fixed in Wheezy: | 899 |
Of these 899 bugs, the following tags are set:
Pending in Wheezy: | 56 |
---|---|
Patched in Wheezy: | 154 |
Duplicates in Wheezy: | 52 |
Can be fixed in a security Update: | 34 |
Contrib or non-free in Wheezy: | 10 |
Claimed in Wheezy: | 0 |
Delayed in Wheezy: | 5 |
Otherwise fixed in Wheezy: | 68 |
Ignoring all the above (multiple tags possible) 595
bugs need to be fixed by Debian Contributors to get Debian 7.0 Wheezy
released.
However, with the view of the Release Managers, 929 need to be dealt with for the release to happen.
Please see Interpreting the
release critical bug statistics
for an explanation of the different numbers.
postet at 14:22 into [Debian/rc-stats/7.0-wheezy] permanent link
Fri, 09 Dec 2011
Release Critical Bug report for Week 49
The bug webinterface of the Ultimate Debian Database currently knows about the following release critical bugs:
In Total: | 1656 |
---|---|
Affecting Wheezy: | 1005 |
Wheezy only: | 156 |
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 Wheezy
released.
However, with the view of the Release Managers, 906 need to be dealt with for the release to happen.
Please see Interpreting the
release critical bug statistics
for an explanation of the different numbers.
postet at 14:03 into [Debian/rc-stats/7.0-wheezy] permanent link
RCBW (Release Critical Bugs of the Week) work flow addendum
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 ;)
postet at 10:50 into [Debian] permanent link
Mon, 05 Dec 2011
Summary from the Bug Squashing Party in Hildesheim
Uff. Two and a half days of hunting release critical bugs ended yesterday evening.
It think it was quite a success. According to the statistics we closed
23 bugs with direct uploads, we created patches for 11, 9 bugs got
solved
by package removals, 6 will be closed by uploads via the
delayed queue, 2 bugs were closed as unreproducible, and 9 other bugs where
closed as well (e.g. already fixed in older version
). On the other
hand we opened 3 and upgraded 6 bugs to be release critical. So in the
end, we solved about...
60 bugs! Wow, I'm really impressed!
I'm also really pleased how well we integrated the newbs
. As I
already mentioned, when planing for this BSP started, we were a bit worried
about the DD / non-dd ratio, but in the end everything worked out very
well. All of those, who registered as interested users
where able
to fix some rc bugs, or help sort out some BTS hickups, e.g. bugs opened
with package a but closed in package b. And as a special pleasure it seems,
that the longest outstanding rc
bug might be fixed soonish, too :)
I'd also like to thank Pengutronix for hosting and sponsoring the BSP! The infrastructure worked very well: You arrived, plugged in your notebook, had a local mirror, IPv6 and fast enough connection to the outside. They also provided lots of snacks, cooked food and drinks (later they complained Debian people won't drink enough; apparently they calculated with way more drinks) and a general good atmosphere.
PS: To the best of my knowledge, it was also the greenest
bug squashing party ever, with most foods and all the electricity coming
from certified ecological production. Cool, eh?
postet at 10:57 into [Debian/events] permanent link