Debian Aims For September Release Date
An anonymous submitter writes "Debian Planet has a good discussion of the most recent release update from the new Debian release managers. The most interesting point is the current hard freeze of base+standard and an optimistic but doable release date in September."
As always, those of you who whine about Debian being out of date have probably never looked at the packages available in unstable and testing. Debian is a very fine distro for even desktop use.
With all that flame war nonsense about communication (which sucks unfortunately in Debian) and AMD64 inclusion in Sarge, it's great that someone has cleared mind and moved forward. No offence to Debian AMD64 guys, thought. But they should at least understand that Sarge release already TOO late.
user@ubuntubox:~$ stfu This server is going down for shutdown NOW!
I think Debian is a fine project, but to be fair you have to admit that the unstable and testing distributions break far too often to use on a production machine. Of course, I've heard that Lindows^H^H^H^Hare and Xandros do a fine job of producing a quality stable release from those packages, but that's not really the same as pure Debian. Using pure Debian is great if you like to tinker and don't mind when things stop working all of a sudden. But for a primary desktop machine it is too unstable and just doesn't cut it for me anymore since I fully ditched mswindows and rely on my linux installation for everyday work.
This isn't to say that Debian sucks -- it really doesn't suck at all and I love using stable for servers. It's just not a "fine desktop" for people who just want to get work or play done without applications suddenly failing on them.
501 Not Implemented
We use Debian on our production kit. I would not like to 'chase' versions with apt daily, weekly or monthly. To us having a stable set of boxes is extremely important, an official release is a big deal to us and the long term plans for our servers are based on these releases.
I used to do apt-get dist-upgrade all the time on my workstation but it is not acceptable for some computers.
1. don't try to track sid every single day.
1(a). this means: apt-get upgrade if and only if there is a serious vulnerability; optionally, once a week, preferably once a month.
2. USE apt-listbugs.
2(a). this means: READ the fscking bugs. take a special look in those marked by apt-listbugs with , but DO read all of them. in any apt-get dist-upgrade, I get at most 30 bugs.
3. USE apt-listchanges.
3(a). yes, you know the drill. READ the changes. SEARCH for changed functionality, especially in packages you tinkered with the config.
1+2+3 == NEVER breaking the machine.
It's better to be the foot on the boot than the face on the pavement. ~~ tkx Kadin2048