If I did everything right, this post will not appear on any RSS feed yet still make it to my blog to maintain history.
The UDD bugs interface currently knows about the following release critical bugs:
- In Total:
1088
- Affecting Jessie:
214 That's the number we need to get down to zero
before the release. They can be split in two big categories:
- Affecting Jessie and unstable:
183 Those need someone to find a fix, or to finish the
work to upload a fix to unstable:
- 43 bugs are tagged 'patch'. Please help by reviewing the patches, and (if you are a DD) by uploading them.
- 15 bugs are marked as done, but still affect unstable. This can happen due to missing builds on some architectures, for example. Help investigate!
- 125 bugs are neither tagged patch, nor marked done. Help make a first step towards resolution!
- Affecting Jessie only: 31 Those are already fixed in unstable, but the fix still needs to migrate to Jessie. You can help by submitting unblock requests for fixed packages, by investigating why packages do not migrate, or by reviewing submitted unblock requests.
- Affecting Jessie and unstable:
183 Those need someone to find a fix, or to finish the
work to upload a fix to unstable:
- Affecting Jessie:
214 That's the number we need to get down to zero
before the release. They can be split in two big categories:
How do we compare to the Squeeze release cycle?
| Week | Squeeze | Wheezy | Diff |
|---|---|---|---|
| 43 | 284 (213+71) | 468 (332+136) | +184 (+119/+65) |
| 44 | 261 (201+60) | 408 (265+143) | +147 (+64/+83) |
| 45 | 261 (205+56) | 425 (291+134) | +164 (+86/+78) |
| 46 | 271 (200+71) | 401 (258+143) | +130 (+58/+72) |
| 47 | 283 (209+74) | 366 (221+145) | +83 (+12/+71) |
| 48 | 256 (177+79) | 378 (230+148) | +122 (+53/+69) |
| 49 | 256 (180+76) | 360 (216+155) | +104 (+36/+79) |
| 50 | 204 (148+56) | 339 (195+144) | +135 (+47/+90) |
| 51 | 178 (124+54) | 323 (190+133) | +145 (+66/+79) |
| 52 | 115 (78+37) | 289 (190+99) | +174 (+112/+62) |
| 1 | 93 (60+33) | 287 (171+116) | +194 (+111/+83) |
| 2 | 82 (46+36) | 271 (162+109) | +189 (+116/+73) |
| 3 | 25 (15+10) | 249 (165+84) | +224 (+150/+74) |
| 4 | 14 (8+6) | 244 (176+68) | +230 (+168/+62) |
| 5 | 2 (0+2) | 224 (132+92) | +222 (+132/+90) |
| 6 | release! | 212 (129+83) | +212 (+129/+83) |
| 7 | release+1 | 194 (128+66) | +194 (+128/+66) |
| 8 | release+2 | 206 (144+62) | +206 (+144/+62) |
| 9 | release+3 | 174 (105+69) | +174 (+105/+69) |
| 10 | release+4 | 120 (72+48) | +120 (+72/+48) |
| 11 | release+5 | 115 (74+41) | +115 (+74/+41) |
| 12 | release+6 | 93 (47+46) | +93 (+47/+46) |
| 13 | release+7 | 50 (24+26) | +50 (+24/+26) |
| 14 | release+8 | 51 (32+19) | +51 (+32/+19) |
| 15 | release+9 | 39 (32+7) | +39 (+32/+7) |
| 16 | release+10 | 20 (12+8) | +20 (+12/+8) |
| 17 | release+11 | 24 (19+5) | +24 (+19/+5) |
| 18 | release+12 | 2 (2+0) | +2 (+2/+0) |
Graphical overview of bug stats thanks to azhag:
Still not sure what to do with this whole thing, but preserving the sharp increase in RC bug count for posterity can't hurt either way. Not sure if it's sad that so many issues may have been overlooked, if this means that Debian is very much alive, either.
The UDD bugs interface currently knows about the following release critical bugs:
- In Total:
1134
- Affecting Jessie:
131 That's the number we need to get down to zero
before the release. They can be split in two big categories:
- Affecting Jessie and unstable:
116 Those need someone to find a fix, or to finish the
work to upload a fix to unstable:
- 16 bugs are tagged 'patch'. Please help by reviewing the patches, and (if you are a DD) by uploading them.
- 8 bugs are marked as done, but still affect unstable. This can happen due to missing builds on some architectures, for example. Help investigate!
- 92 bugs are neither tagged patch, nor marked done. Help make a first step towards resolution!
- Affecting Jessie only: 15 Those are already fixed in unstable, but the fix still needs to migrate to Jessie. You can help by submitting unblock requests for fixed packages, by investigating why packages do not migrate, or by reviewing submitted unblock requests.
- Affecting Jessie and unstable:
116 Those need someone to find a fix, or to finish the
work to upload a fix to unstable:
- Affecting Jessie:
131 That's the number we need to get down to zero
before the release. They can be split in two big categories:
How do we compare to the Squeeze release cycle?
| Week | Squeeze | Wheezy | Diff |
|---|---|---|---|
| 43 | 284 (213+71) | 468 (332+136) | +184 (+119/+65) |
| 44 | 261 (201+60) | 408 (265+143) | +147 (+64/+83) |
| 45 | 261 (205+56) | 425 (291+134) | +164 (+86/+78) |
| 46 | 271 (200+71) | 401 (258+143) | +130 (+58/+72) |
| 47 | 283 (209+74) | 366 (221+145) | +83 (+12/+71) |
| 48 | 256 (177+79) | 378 (230+148) | +122 (+53/+69) |
| 49 | 256 (180+76) | 360 (216+155) | +104 (+36/+79) |
| 50 | 204 (148+56) | 339 (195+144) | +135 (+47/+90) |
| 51 | 178 (124+54) | 323 (190+133) | +145 (+66/+79) |
| 52 | 115 (78+37) | 289 (190+99) | +174 (+112/+62) |
| 1 | 93 (60+33) | 287 (171+116) | +194 (+111/+83) |
| 2 | 82 (46+36) | 271 (162+109) | +189 (+116/+73) |
| 3 | 25 (15+10) | 249 (165+84) | +224 (+150/+74) |
| 4 | 14 (8+6) | 244 (176+68) | +230 (+168/+62) |
| 5 | 2 (0+2) | 224 (132+92) | +222 (+132/+90) |
| 6 | release! | 212 (129+83) | +212 (+129/+83) |
| 7 | release+1 | 194 (128+66) | +194 (+128/+66) |
| 8 | release+2 | 206 (144+62) | +206 (+144/+62) |
| 9 | release+3 | 174 (105+69) | +174 (+105/+69) |
| 10 | release+4 | 120 (72+48) | +120 (+72/+48) |
| 11 | release+5 | 115 (74+41) | +115 (+74/+41) |
| 12 | release+6 | 93 (47+46) | +93 (+47/+46) |
| 13 | release+7 | 50 (24+26) | +50 (+24/+26) |
| 14 | release+8 | 51 (32+19) | +51 (+32/+19) |
| 15 | release+9 | 39 (32+7) | +39 (+32/+7) |
| 16 | release+10 | 20 (12+8) | +20 (+12/+8) |
| 17 | release+11 | 24 (19+5) | +24 (+19/+5) |
| 18 | release+12 | 2 (2+0) | +2 (+2/+0) |
Graphical overview of bug stats thanks to azhag:
Releezy
Tomorrow morning at around 0900 UTC, a lot of very dedicated people will start working on the actual release of Debian 7.0 (wheezy).
A huge thank you to everyone who worked on getting Debian to this point.
I for one welcome our new penguin overlord!
Housekeeping
These will obviously be the last rc bug stats in this release cycle. I am still unsure what to do with this particular series until the next freeze and feedback would be appreciated. Possible approaches are continuing as is, putting this into its own specific feed, decreasing the frequency to once a month, or to simply stop until jessie is frozen. An ikiwiki poll may be overkill. Or not.
Remaining bugs
As of right now, there are two bugs open:
- #645713 - "apt" - many squeeze->wheezy upgrades fail with "Could not perform immediate configuration"
- #706641 - "apt, libgd-text-perl" - apt, libgd-text-perl: fails to upgrade from squeeze: Could not perform immediate configuration on 'libgd-gd2-perl'.
Both relate to weird behaviour by apt when upgrading from squeeze to wheezy. These bugs will not be truly closed, but merely ignored, for wheezy's release. If you happen to encounter the message above, it's best to consult the release notes for possible workarounds.
Stats
The UDD bugs interface currently knows about the following release critical bugs:
- In Total:
738
- Affecting wheezy:
2 That's the number we need to get down to zero before
the release. They can be split in two big categories:
- Affecting wheezy and unstable:
2 Those need someone to find a fix, or to finish the
work to upload a fix to unstable:
- 0 bugs are tagged 'patch'. Please help by reviewing the patches, and (if you are a DD) by uploading them.
- 0 bugs are marked as done, but still affect unstable. This can happen due to missing builds on some architectures, for example. Help investigate!
- 2 bugs are neither tagged patch, nor marked done. Help make a first step towards resolution!
- Affecting wheezy only: 0 Those are already fixed in unstable, but the fix still needs to migrate to wheezy. You can help by submitting unblock requests for fixed packages, by investigating why packages do not migrate, or by reviewing submitted unblock requests.
- Affecting wheezy and unstable:
2 Those need someone to find a fix, or to finish the
work to upload a fix to unstable:
- Affecting wheezy:
2 That's the number we need to get down to zero before
the release. They can be split in two big categories:
How do we compare to the Squeeze release cycle?
| Week | Squeeze | Wheezy | Diff |
|---|---|---|---|
| 43 | 284 (213+71) | 468 (332+136) | +184 (+119/+65) |
| 44 | 261 (201+60) | 408 (265+143) | +147 (+64/+83) |
| 45 | 261 (205+56) | 425 (291+134) | +164 (+86/+78) |
| 46 | 271 (200+71) | 401 (258+143) | +130 (+58/+72) |
| 47 | 283 (209+74) | 366 (221+145) | +83 (+12/+71) |
| 48 | 256 (177+79) | 378 (230+148) | +122 (+53/+69) |
| 49 | 256 (180+76) | 360 (216+155) | +104 (+36/+79) |
| 50 | 204 (148+56) | 339 (195+144) | +135 (+47/+90) |
| 51 | 178 (124+54) | 323 (190+133) | +145 (+66/+79) |
| 52 | 115 (78+37) | 289 (190+99) | +174 (+112/+62) |
| 1 | 93 (60+33) | 287 (171+116) | +194 (+111/+83) |
| 2 | 82 (46+36) | 271 (162+109) | +189 (+116/+73) |
| 3 | 25 (15+10) | 249 (165+84) | +224 (+150/+74) |
| 4 | 14 (8+6) | 244 (176+68) | +230 (+168/+62) |
| 5 | 2 (0+2) | 224 (132+92) | +222 (+132/+90) |
| 6 | release! | 212 (129+83) | +212 (+129/+83) |
| 7 | release+1 | 194 (128+66) | +194 (+128/+66) |
| 8 | release+2 | 206 (144+62) | +206 (+144/+62) |
| 9 | release+3 | 174 (105+69) | +174 (+105/+69) |
| 10 | release+4 | 120 (72+48) | +120 (+72/+48) |
| 11 | release+5 | 115 (74+41) | +115 (+74/+41) |
| 12 | release+6 | 93 (47+46) | +93 (+47/+46) |
| 13 | release+7 | 50 (24+26) | +50 (+24/+26) |
| 14 | release+8 | 51 (32+19) | +51 (+32/+19) |
| 15 | release+9 | 39 (32+7) | +39 (+32/+7) |
| 16 | release+10 | 20 (12+8) | +20 (+12/+8) |
| 17 | release+11 | 24 (19+5) | +24 (+19/+5) |
| 18 | release+12 | 2 (2+0) | +2 (+2/+0) |
Graphical overview of bug stats thanks to azhag:
There's a #newinwheezy game which basically presents a few of the 4451 new source packages in Debian/wheezy to a wider audience.
My own entry is, obviously, vcsh.
Quoth the manpage
vcsh - manage config files in $HOME via fake bare git repositories
You can also consult the (somewhat outdated) readme or just clone it.
In related news, I have been asked to hold my "Gitify your life" talk at LinuxTag 2013. This talk can be found here. While the text on that page is in German, all slides will be in English and I will happily use either language based on what the audience prefers.
The UDD bugs interface currently knows about the following release critical bugs:
- In Total:
728
- Affecting wheezy:
24 That's the number we need to get down to zero
before the release. They can be split in two big categories:
- Affecting wheezy and unstable:
19 Those need someone to find a fix, or to finish the
work to upload a fix to unstable:
- 0 bugs are tagged 'patch'. Please help by reviewing the patches, and (if you are a DD) by uploading them.
- 1 bugs are marked as done, but still affect unstable. This can happen due to missing builds on some architectures, for example. Help investigate!
- 18 bugs are neither tagged patch, nor marked done. Help make a first step towards resolution!
- Affecting wheezy only: 5 Those are already fixed in unstable, but the fix still needs to migrate to wheezy. You can help by submitting unblock requests for fixed packages, by investigating why packages do not migrate, or by reviewing submitted unblock requests.
- Affecting wheezy and unstable:
19 Those need someone to find a fix, or to finish the
work to upload a fix to unstable:
- Affecting wheezy:
24 That's the number we need to get down to zero
before the release. They can be split in two big categories:
How do we compare to the Squeeze release cycle?
| Week | Squeeze | Wheezy | Diff |
|---|---|---|---|
| 43 | 284 (213+71) | 468 (332+136) | +184 (+119/+65) |
| 44 | 261 (201+60) | 408 (265+143) | +147 (+64/+83) |
| 45 | 261 (205+56) | 425 (291+134) | +164 (+86/+78) |
| 46 | 271 (200+71) | 401 (258+143) | +130 (+58/+72) |
| 47 | 283 (209+74) | 366 (221+145) | +83 (+12/+71) |
| 48 | 256 (177+79) | 378 (230+148) | +122 (+53/+69) |
| 49 | 256 (180+76) | 360 (216+155) | +104 (+36/+79) |
| 50 | 204 (148+56) | 339 (195+144) | +135 (+47/+90) |
| 51 | 178 (124+54) | 323 (190+133) | +145 (+66/+79) |
| 52 | 115 (78+37) | 289 (190+99) | +174 (+112/+62) |
| 1 | 93 (60+33) | 287 (171+116) | +194 (+111/+83) |
| 2 | 82 (46+36) | 271 (162+109) | +189 (+116/+73) |
| 3 | 25 (15+10) | 249 (165+84) | +224 (+150/+74) |
| 4 | 14 (8+6) | 244 (176+68) | +230 (+168/+62) |
| 5 | 2 (0+2) | 224 (132+92) | +222 (+132/+90) |
| 6 | release! | 212 (129+83) | +212 (+129/+83) |
| 7 | release+1 | 194 (128+66) | +194 (+128/+66) |
| 8 | release+2 | 206 (144+62) | +206 (+144/+62) |
| 9 | release+3 | 174 (105+69) | +174 (+105/+69) |
| 10 | release+4 | 120 (72+48) | +120 (+72/+48) |
| 11 | release+5 | 115 (74+41) | +115 (+74/+41) |
| 12 | release+6 | 93 (47+46) | +93 (+47/+46) |
| 13 | release+7 | 50 (24+26) | +50 (+24/+26) |
| 14 | release+8 | 51 (32+19) | +51 (+32/+19) |
| 15 | release+9 | 39 (32+7) | +39 (+32/+7) |
| 16 | release+10 | 20 (12+8) | +20 (+12/+8) |
| 17 | release+11 | 24 (19+5) | +24 (+19/+5) |
| 18 | release+12 |
Graphical overview of bug stats thanks to azhag:
Seems I was off by two weeks. Week 18, it is/should be. Yay.
The UDD bugs interface currently knows about the following release critical bugs:
- In Total:
716
- Affecting wheezy:
20 That's the number we need to get down to zero
before the release. They can be split in two big categories:
- Affecting wheezy and unstable:
12 Those need someone to find a fix, or to finish the
work to upload a fix to unstable:
- 4 bugs are tagged 'patch'. Please help by reviewing the patches, and (if you are a DD) by uploading them.
- 2 bugs are marked as done, but still affect unstable. This can happen due to missing builds on some architectures, for example. Help investigate!
- 6 bugs are neither tagged patch, nor marked done. Help make a first step towards resolution!
- Affecting wheezy only: 8 Those are already fixed in unstable, but the fix still needs to migrate to wheezy. You can help by submitting unblock requests for fixed packages, by investigating why packages do not migrate, or by reviewing submitted unblock requests.
- Affecting wheezy and unstable:
12 Those need someone to find a fix, or to finish the
work to upload a fix to unstable:
- Affecting wheezy:
20 That's the number we need to get down to zero
before the release. They can be split in two big categories:
How do we compare to the Squeeze release cycle?
| Week | Squeeze | Wheezy | Diff |
|---|---|---|---|
| 43 | 284 (213+71) | 468 (332+136) | +184 (+119/+65) |
| 44 | 261 (201+60) | 408 (265+143) | +147 (+64/+83) |
| 45 | 261 (205+56) | 425 (291+134) | +164 (+86/+78) |
| 46 | 271 (200+71) | 401 (258+143) | +130 (+58/+72) |
| 47 | 283 (209+74) | 366 (221+145) | +83 (+12/+71) |
| 48 | 256 (177+79) | 378 (230+148) | +122 (+53/+69) |
| 49 | 256 (180+76) | 360 (216+155) | +104 (+36/+79) |
| 50 | 204 (148+56) | 339 (195+144) | +135 (+47/+90) |
| 51 | 178 (124+54) | 323 (190+133) | +145 (+66/+79) |
| 52 | 115 (78+37) | 289 (190+99) | +174 (+112/+62) |
| 1 | 93 (60+33) | 287 (171+116) | +194 (+111/+83) |
| 2 | 82 (46+36) | 271 (162+109) | +189 (+116/+73) |
| 3 | 25 (15+10) | 249 (165+84) | +224 (+150/+74) |
| 4 | 14 (8+6) | 244 (176+68) | +230 (+168/+62) |
| 5 | 2 (0+2) | 224 (132+92) | +222 (+132/+90) |
| 6 | release! | 212 (129+83) | +212 (+129/+83) |
| 7 | release+1 | 194 (128+66) | +194 (+128/+66) |
| 8 | release+2 | 206 (144+62) | +206 (+144/+62) |
| 9 | release+3 | 174 (105+69) | +174 (+105/+69) |
| 10 | release+4 | 120 (72+48) | +120 (+72/+48) |
| 11 | release+5 | 115 (74+41) | +115 (+74/+41) |
| 12 | release+6 | 93 (47+46) | +93 (+47/+46) |
| 13 | release+7 | 50 (24+26) | +50 (+24/+26) |
| 14 | release+8 | 51 (32+19) | +51 (+32/+19) |
| 15 | release+9 | 39 (32+7) | +39 (+32/+7) |
| 16 | release+10 | 20 (12+8) | +20 (+12/+8) |
| 17 | release+11 | ||
| 18 | release+12 |
Graphical overview of bug stats thanks to azhag:
This week: Monday 47, Tuesday 47, Wednesday 41, Thursday 39, Friday 37
Addendum: the bug count was at 37 around Friday noon and that's what I am tracking with the short stats above.
The UDD bugs interface currently knows about the following release critical bugs:
- In Total:
717
- Affecting wheezy:
39 That's the number we need to get down to zero
before the release. They can be split in two big categories:
- Affecting wheezy and unstable:
32 Those need someone to find a fix, or to finish the
work to upload a fix to unstable:
- 11 bugs are tagged 'patch'. Please help by reviewing the patches, and (if you are a DD) by uploading them.
- 2 bugs are marked as done, but still affect unstable. This can happen due to missing builds on some architectures, for example. Help investigate!
- 19 bugs are neither tagged patch, nor marked done. Help make a first step towards resolution!
- Affecting wheezy only: 7 Those are already fixed in unstable, but the fix still needs to migrate to wheezy. You can help by submitting unblock requests for fixed packages, by investigating why packages do not migrate, or by reviewing submitted unblock requests.
- Affecting wheezy and unstable:
32 Those need someone to find a fix, or to finish the
work to upload a fix to unstable:
- Affecting wheezy:
39 That's the number we need to get down to zero
before the release. They can be split in two big categories:
How do we compare to the Squeeze release cycle?
| Week | Squeeze | Wheezy | Diff |
|---|---|---|---|
| 43 | 284 (213+71) | 468 (332+136) | +184 (+119/+65) |
| 44 | 261 (201+60) | 408 (265+143) | +147 (+64/+83) |
| 45 | 261 (205+56) | 425 (291+134) | +164 (+86/+78) |
| 46 | 271 (200+71) | 401 (258+143) | +130 (+58/+72) |
| 47 | 283 (209+74) | 366 (221+145) | +83 (+12/+71) |
| 48 | 256 (177+79) | 378 (230+148) | +122 (+53/+69) |
| 49 | 256 (180+76) | 360 (216+155) | +104 (+36/+79) |
| 50 | 204 (148+56) | 339 (195+144) | +135 (+47/+90) |
| 51 | 178 (124+54) | 323 (190+133) | +145 (+66/+79) |
| 52 | 115 (78+37) | 289 (190+99) | +174 (+112/+62) |
| 1 | 93 (60+33) | 287 (171+116) | +194 (+111/+83) |
| 2 | 82 (46+36) | 271 (162+109) | +189 (+116/+73) |
| 3 | 25 (15+10) | 249 (165+84) | +224 (+150/+74) |
| 4 | 14 (8+6) | 244 (176+68) | +230 (+168/+62) |
| 5 | 2 (0+2) | 224 (132+92) | +222 (+132/+90) |
| 6 | release! | 212 (129+83) | +212 (+129/+83) |
| 7 | release+1 | 194 (128+66) | +194 (+128/+66) |
| 8 | release+2 | 206 (144+62) | +206 (+144/+62) |
| 9 | release+3 | 174 (105+69) | +174 (+105/+69) |
| 10 | release+4 | 120 (72+48) | +120 (+72/+48) |
| 11 | release+5 | 115 (74+41) | +115 (+74/+41) |
| 12 | release+6 | 93 (47+46) | +93 (+47/+46) |
| 13 | release+7 | 50 (24+26) | +50 (+24/+26) |
| 14 | release+8 | 51 (32+19) | +51 (+32/+19) |
| 15 | release+9 | 39 (32+7) | +39 (+32/+7) |
| 16 | release+10 | ||
| 17 | release+11 | ||
| 18 | release+12 |
Graphical overview of bug stats thanks to azhag:
Over the week, around noon CEST, we had:
- Monday: 44 total
- Tuesday 43 total
- Wednesday: 49 total
- Thursday: 53 total
The UDD bugs interface currently knows about the following release critical bugs:
- In Total:
718
- Affecting wheezy:
51 That's the number we need to get down to zero
before the release. They can be split in two big categories:
- Affecting wheezy and unstable:
32 Those need someone to find a fix, or to finish the
work to upload a fix to unstable:
- 9 bugs are tagged 'patch'. Please help by reviewing the patches, and (if you are a DD) by uploading them.
- 1 bugs are marked as done, but still affect unstable. This can happen due to missing builds on some architectures, for example. Help investigate!
- 22 bugs are neither tagged patch, nor marked done. Help make a first step towards resolution!
- Affecting wheezy only: 19 Those are already fixed in unstable, but the fix still needs to migrate to wheezy. You can help by submitting unblock requests for fixed packages, by investigating why packages do not migrate, or by reviewing submitted unblock requests.
- Affecting wheezy and unstable:
32 Those need someone to find a fix, or to finish the
work to upload a fix to unstable:
- Affecting wheezy:
51 That's the number we need to get down to zero
before the release. They can be split in two big categories:
How do we compare to the Squeeze release cycle?
| Week | Squeeze | Wheezy | Diff |
|---|---|---|---|
| 43 | 284 (213+71) | 468 (332+136) | +184 (+119/+65) |
| 44 | 261 (201+60) | 408 (265+143) | +147 (+64/+83) |
| 45 | 261 (205+56) | 425 (291+134) | +164 (+86/+78) |
| 46 | 271 (200+71) | 401 (258+143) | +130 (+58/+72) |
| 47 | 283 (209+74) | 366 (221+145) | +83 (+12/+71) |
| 48 | 256 (177+79) | 378 (230+148) | +122 (+53/+69) |
| 49 | 256 (180+76) | 360 (216+155) | +104 (+36/+79) |
| 50 | 204 (148+56) | 339 (195+144) | +135 (+47/+90) |
| 51 | 178 (124+54) | 323 (190+133) | +145 (+66/+79) |
| 52 | 115 (78+37) | 289 (190+99) | +174 (+112/+62) |
| 1 | 93 (60+33) | 287 (171+116) | +194 (+111/+83) |
| 2 | 82 (46+36) | 271 (162+109) | +189 (+116/+73) |
| 3 | 25 (15+10) | 249 (165+84) | +224 (+150/+74) |
| 4 | 14 (8+6) | 244 (176+68) | +230 (+168/+62) |
| 5 | 2 (0+2) | 224 (132+92) | +222 (+132/+90) |
| 6 | release! | 212 (129+83) | +212 (+129/+83) |
| 7 | release+1 | 194 (128+66) | +194 (+128/+66) |
| 8 | release+2 | 206 (144+62) | +206 (+144/+62) |
| 9 | release+3 | 174 (105+69) | +174 (+105/+69) |
| 10 | release+4 | 120 (72+48) | +120 (+72/+48) |
| 11 | release+5 | 115 (74+41) | +115 (+74/+41) |
| 12 | release+6 | 93 (47+46) | +93 (+47/+46) |
| 13 | release+7 | 50 (24+26) | +50 (+24/+26) |
| 14 | release+8 | 51 (32+19) | +51 (+32/+19) |
| 15 | release+9 | ||
| 16 | release+10 | ||
| 17 | release+11 | ||
| 18 | release+12 |
Graphical overview of bug stats thanks to azhag:
Hallowed fornicating kúluskítur, Chiroptera Sapiens Sapiens!
Look at that corrected bug count... It seems week 16, or even week 15, will really be the week of the penguin!
The UDD bugs interface currently knows about the following release critical bugs:
- In Total:
704
- Affecting wheezy:
50 That's the number we need to get down to zero
before the release. They can be split in two big categories:
- Affecting wheezy and unstable:
24 Those need someone to find a fix, or to finish the
work to upload a fix to unstable:
- 6 bugs are tagged 'patch'. Please help by reviewing the patches, and (if you are a DD) by uploading them.
- 3 bugs are marked as done, but still affect unstable. This can happen due to missing builds on some architectures, for example. Help investigate!
- 15 bugs are neither tagged patch, nor marked done. Help make a first step towards resolution!
- Affecting wheezy only: 26 Those are already fixed in unstable, but the fix still needs to migrate to wheezy. You can help by submitting unblock requests for fixed packages, by investigating why packages do not migrate, or by reviewing submitted unblock requests.
- Affecting wheezy and unstable:
24 Those need someone to find a fix, or to finish the
work to upload a fix to unstable:
- Affecting wheezy:
50 That's the number we need to get down to zero
before the release. They can be split in two big categories:
How do we compare to the Squeeze release cycle?
| Week | Squeeze | Wheezy | Diff |
|---|---|---|---|
| 43 | 284 (213+71) | 468 (332+136) | +184 (+119/+65) |
| 44 | 261 (201+60) | 408 (265+143) | +147 (+64/+83) |
| 45 | 261 (205+56) | 425 (291+134) | +164 (+86/+78) |
| 46 | 271 (200+71) | 401 (258+143) | +130 (+58/+72) |
| 47 | 283 (209+74) | 366 (221+145) | +83 (+12/+71) |
| 48 | 256 (177+79) | 378 (230+148) | +122 (+53/+69) |
| 49 | 256 (180+76) | 360 (216+155) | +104 (+36/+79) |
| 50 | 204 (148+56) | 339 (195+144) | +135 (+47/+90) |
| 51 | 178 (124+54) | 323 (190+133) | +145 (+66/+79) |
| 52 | 115 (78+37) | 289 (190+99) | +174 (+112/+62) |
| 1 | 93 (60+33) | 287 (171+116) | +194 (+111/+83) |
| 2 | 82 (46+36) | 271 (162+109) | +189 (+116/+73) |
| 3 | 25 (15+10) | 249 (165+84) | +224 (+150/+74) |
| 4 | 14 (8+6) | 244 (176+68) | +230 (+168/+62) |
| 5 | 2 (0+2) | 224 (132+92) | +222 (+132/+90) |
| 6 | release! | 212 (129+83) | +212 (+129/+83) |
| 7 | release+1 | 194 (128+66) | +194 (+128/+66) |
| 8 | release+2 | 206 (144+62) | +206 (+144/+62) |
| 9 | release+3 | 174 (105+69) | +174 (+105/+69) |
| 10 | release+4 | 120 (72+48) | +120 (+72/+48) |
| 11 | release+5 | 115 (74+41) | +115 (+74/+41) |
| 12 | release+6 | 93 (47+46) | +93 (+47/+46) |
| 13 | release+7 | 50 (24+26) | +50 (+24/+26) |
| 14 | release+8 | ||
| 15 | release+9 | ||
| 16 | release+10 | ||
| 17 | release+11 | ||
| 18 | release+12 |
Graphical overview of bug stats thanks to azhag:
Let's see if we will have 82 open bugs next week ;)
Current trend points towards week 16/17.
The UDD bugs interface currently knows about the following release critical bugs:
- In Total:
718
- Affecting wheezy:
93 That's the number we need to get down to zero
before the release. They can be split in two big categories:
- Affecting wheezy and unstable:
47 Those need someone to find a fix, or to finish the
work to upload a fix to unstable:
- 16 bugs are tagged 'patch'. Please help by reviewing the patches, and (if you are a DD) by uploading them.
- 9 bugs are marked as done, but still affect unstable. This can happen due to missing builds on some architectures, for example. Help investigate!
- 27 bugs are neither tagged patch, nor marked done. Help make a first step towards resolution!
- Affecting wheezy only: 46 Those are already fixed in unstable, but the fix still needs to migrate to wheezy. You can help by submitting unblock requests for fixed packages, by investigating why packages do not migrate, or by reviewing submitted unblock requests.
- Affecting wheezy and unstable:
47 Those need someone to find a fix, or to finish the
work to upload a fix to unstable:
- Affecting wheezy:
93 That's the number we need to get down to zero
before the release. They can be split in two big categories:
How do we compare to the Squeeze release cycle?
| Week | Squeeze | Wheezy | Diff |
|---|---|---|---|
| 43 | 284 (213+71) | 468 (332+136) | +184 (+119/+65) |
| 44 | 261 (201+60) | 408 (265+143) | +147 (+64/+83) |
| 45 | 261 (205+56) | 425 (291+134) | +164 (+86/+78) |
| 46 | 271 (200+71) | 401 (258+143) | +130 (+58/+72) |
| 47 | 283 (209+74) | 366 (221+145) | +83 (+12/+71) |
| 48 | 256 (177+79) | 378 (230+148) | +122 (+53/+69) |
| 49 | 256 (180+76) | 360 (216+155) | +104 (+36/+79) |
| 50 | 204 (148+56) | 339 (195+144) | +135 (+47/+90) |
| 51 | 178 (124+54) | 323 (190+133) | +145 (+66/+79) |
| 52 | 115 (78+37) | 289 (190+99) | +174 (+112/+62) |
| 1 | 93 (60+33) | 287 (171+116) | +194 (+111/+83) |
| 2 | 82 (46+36) | 271 (162+109) | +189 (+116/+73) |
| 3 | 25 (15+10) | 249 (165+84) | +224 (+150/+74) |
| 4 | 14 (8+6) | 244 (176+68) | +230 (+168/+62) |
| 5 | 2 (0+2) | 224 (132+92) | +222 (+132/+90) |
| 6 | release! | 212 (129+83) | +212 (+129/+83) |
| 7 | release+1 | 194 (128+66) | +194 (+128/+66) |
| 8 | release+2 | 206 (144+62) | +206 (+144/+62) |
| 9 | release+3 | 174 (105+69) | +174 (+105/+69) |
| 10 | release+4 | 120 (72+48) | +120 (+72/+48) |
| 11 | release+5 | 115 (74+41) | +115 (+74/+41) |
| 12 | release+6 | 93 (47+46) | +93 (+47/+46) |
| 13 | release+7 | ||
| 14 | release+8 | ||
| 15 | release+9 | ||
| 16 | release+10 | ||
| 17 | release+11 | ||
| 18 | release+12 |
Graphical overview of bug stats thanks to azhag:
