As I am patently lazy, I hacked together a little helper in perl which outputs the page I am just adding to by writing this. It's a tad hackish inasmuch I don't bother to transform the HTML into anything and simply embedd it in the Markdown, but it's working well enough for now. In the medium term, I am hoping to add some nice graphs as per azhag's suggestion, but they didn't get back to me, yet.
A warning to anyone not subscribed to Planet Debian and reading this via a different aggregator: You will still see weekly stats from now on which may or may not be interesting to you. In case you object, please leave a comment or poke me directly.
The UDD bugs interface currently knows about the following release critical bugs:
- In Total:
- Affecting wheezy:
408 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:
265 Those need someone to find a fix, or to finish the
work to upload a fix to unstable:
- 64 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!
- 194 bugs are neither tagged patch, nor marked done. Help make a first step towards resolution!
- Affecting wheezy only: 143 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: 265 Those need someone to find a fix, or to finish the work to upload a fix to unstable:
- Affecting wheezy: 408 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 cycle ?
|43||284 (213+71)||468 (332+136)||+184 (+119 ; +65)|