Linked by Thom Holwerda on Fri 23rd Feb 2007 17:38 UTC, submitted by anonymous
Debian and its clones Last September, some of the Debian Linux distribution's leadership wanted to make sure that Etch, the next version of Debian, arrived on its December 4th due date. Almost two months later, though, according to the February 17th Release Critical Bug Report memo to the Debian Developers Announcement list, there are still 541 release critical bugs.
Permalink for comment 216152
To read all comments associated with this story, please click here.
Member since:

Imagine if Debian unstable were "stabilized" once every month (or 2 weeks or 2 months, whatever works). If a package didn't make it in one month, no problem, wait 'til next release window (e.g. 1 month).

That would kill Debian for anything but casual use. The beauty of Debian stable is that you can do a apt-get update && apt-get upgrade and have the latest version of stable and secure packages. Now this comes down to one thing, configurations are NOT broken. Look at how the current stable would handle an upgrade to the latest clamav, it wouldn't. You have to manually fiddle the config files simply because overwriting and/or merging the new conf-files is a really shitty idea if you run more than a few servers.

Stable is stable for a reason, if you want the latest and greatest you run unstable or testing (etch).

Ubuntu is very nice but stuff breaks in far too many ways in between releases and that takes away some of the fun.

And yes, we run 100+ Debian servers at work, and my workstation is Ubuntu (which btw has piss-poor interactivity compared to my older and slower FreeBSD-Gnome laptop).

Edited 2007-02-24 13:38

Reply Parent Score: 1