Slashdot Mirror

Umm thats bugs that only apply to lenny and not to sid. For all "rc" bugs you want http://bts.turmzimmer.net/details.php?bydist=lenny&sortby=packages&new=7&refresh=1800

More like 5 RC bugs.

> What about release critical bugs? Currently there are 173 of them
Better take a look at http://bts.turmzimmer.net/graph-large.png, which provides more accurate stats.

> I thought that they won't be releasing next version before they are fixed. And even with optimal speed it
> looks like it would take at least 1,5 months to get them all fixed.

Packages with RC bugs can either be fixed or removed, it's always been that way.

Last time I looked, it was here, but as that page says this is an unofficial list.
Methinks some of the bugs look bad, but at least you can *see* what's happening "in the kitchen" with Debian.

Some explanations about how to count:

The official release-critical bug tracker[1] is still not updated to handle "versioned bug-reports". Meaning it counts _all_ open bug reports, while in reality the bug might be "closed" in the _version_ of the package in Etch but the entire bug in not closed (because it still effects Sarge and older?). So the official sources are a bit misleading.
A debian developer called "Sesse" has an updated tracker[2]. This one gives a bit better indication about the truth. Hopefully his code will be moved over to become the official version.
As also previously mentioned, Andreas "aba" Barth has his own bug tracking tool[3]. This gives a bit more information about each release-critical bug and has filtering capabilities.
All sources indicate that there are many "RC" bugs left, but using aba's tool[3] you can see that most open bug reports are security issues. Security issues will come up all the time. There is already infrastructure in place to provide security updates for the stable distribution, so there's no need to hold back the release because of these issues as they can be fixed at any time.
The few remaining issues are new bugs that has just recently surfaces and hasn't yet been analyzed. They might have a too high severity set, noone knows until they have been analyzed. This also doesn't give much reason to hold back the released, there will always be a few really new bugs that there hasn't been time to analyze yet.
All in all, having all bugs fixed looks promising, even if noone can promise that the CD-images are 100% bug-free.

[1] http://bugs.debian.org/release-critical/
[2] http://people.debian.org/~sesse/bugscan/
[3] http://bts.turmzimmer.net/details.php?bydist=etch

Regards,
fatal

The bugs tagged with 'security' are probably not important enough to delay the release. They can be fixed at any time with an update from the security team. That leaves five bugs, none of which seem so important that they can't be fixed for 4.0r1.

I can still see 17 release-critical bugs in their bugtracker: http://bts.turmzimmer.net/details.php?bydist=etch

Have they decided to postpone their resolution until R2?

1. Cut the distro down to what will fit on one CD (two max). That will reduce a lot of Debian's headaches. Less for them to maintain and less to test between releases. Everything else can be put into contributed non-official repositories
2. Don't be so anal and patch-happy with mainstream packages. Big projects like Gnome and KDE already do extensive testing upstream. Those packages should be able to move more quickly through the unstable-testing-stable cycle without sacrificing stability or extensive patching. How much of the debian patching on these type of big projects is *really* functionally necessary versus "I 'm the debian package mantainer and I want to put my mark on it".

here: http://bts.turmzimmer.net/details.php

The June 6 date still depends on how fast the level will drop -- at the time of writing, it is at 17 RC bugs, it will have to be at 0 on June 3, so they have some work to do.

Security support is already in place, though, so there is not really a reason to hold off upgrading :)

Jan