Two Major Debian Releases In One Day
AndyCater writes "If all goes according to plan, Debian should release both an update to Debian Sarge (3.1r6, henceforth to be oldstable) and a new stable release (Debian 4.0, which was codenamed Etch) — and announce the results of the election for Debian Project Leader — all within 12 hours. Sarge was updated late on April 7th UTC, Sam Hocevar was announced as DPL at about 00:30 UTC, and preparations for the release of Debian Etch are ongoing and look good for later on the 8th."
I don't know if the Universe can withstand that.
Sam Hocevar won the Debian Project Leader election by 8 votes over Steve McIntyre
western nations base their entire diet around bread, so passover takes a huge chunk out of nerd diets (i know first hand), so to compensate for the scarcity of kosher food, they must have guzzled more caffeinated beverages.. thus resulting in the warp speed rush to 4.0 ..
well that's at least my theory : D
VLC FOR MAC IS DYING! IF YOU DEVELOP, PLEASE SAVE IT!!
Cue the:
Two releases in one day! This is like a turtle suddenly accelerating to lightspeed. It should shut up the people who say the Debian cycle is slow! Good thing they've nearly caught up to Windows; only 2.0 more versions to go!
In all seriousness, this stable came out over a year more quickly than 3.0 -> 3.1. That's nice to see. I'm looking forward to giving it a whirl.
It depends on your /etc/apt/sources.list.
Each line will either end with the word "Etch" or "Testing".
If it ends with Etch, then you will stay with Etch (Stable).
If it ends with Testing, then you will start getting the new Testing packages.
Probably the best thing to do is to stay with Etch for a couple of months while the new Testing settles down, then dist-upgrade back to Testing.
A house divided against itself cannot stand.
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