Sarge is Now Frozen
JoeBuck writes "Steve Langasek has announced that Debian Sarge is now frozen. He produced a schedule that would lead to a Debian release at the end of May, though I would expect it to slip somewhat. I'm glad that the long wait for a Debian release will soon be over."
I was upset to see that KDE 3.4 was being held back from Sid until Sarge released (I ended up getting it from the Kubuntu sources), and I believe a few other packages followed this policy as well. Now that Sarge is coming out I assume we'll see some major updates in Sid. On that note, does anyone know when Debian will adopt X.org?
I wonder if the Debian team with move to quicker release cycles after Sarge gets out the door. Wasn't that one of the goals of the new Debian project leader?
It means Sarge is a big step closer to becomming the stable branch. Freeze severely narrows the criterea for updates to enter testing; they're now hand-picked by necessity rather than appearing automatically once they've survived unstable long enough. It's the last big step before a release; at that point, Sarge will become Stable.
The comparing methaphor is indeed appropriate, because Debian is a complete software distribution, not just an OS. The equivalent situation would be Microsoft not updating any of their software for three years.
Also, Windows XP SP2 could well be considered a release of its own, considering the depth and breath of the changes (as well as the widespread application breakage).
... to warn people who follow the link not to make plans that rely on the May 30th date. Your suggestion that expecting a further slip differs from common sense is off target. It is no insult to Debian to expect that the RC bug count won't get to zero without a hitch.
such nonsense is not what one would expect form a 5 digit slashdotter.
Us in the five digit club can put out nonsense as good as the next slashdotter. Only difference is we got more practice!
Can I get an eye poke?
Dog House Forum
I think its really dissapointing when I read all of the flamebait on this thread.
/. readers want to denigrate all of the hardwork that those at debian have been doing because the release cycle doesn't give them exactly what they want.
I've been a loyal debian user for a while and I happen to like the system which they use to control the level of stability/upgradeability that your willing to tolerate.
Furthermore, its just on of the many models of Open Source. I think it is good to have diversity. I have a hard time believing that this many
If its not what you want great, go elsewhere, but leave quietly not bitching about how it doesnt suit *your* needs.
Not everyone has the same experience, but I recently (~1 year ago) switched from Fedora to Debian and I'm pretty happy. Basically, I found that Debian *unstable* was much more reliable than Fedora Core 2 (release).
Opus: the Swiss army knife of audio codec
And now it is my turn to disagree. When you start talking about the enterprise, a whole different set of rules come in to play.
Why is Windows NT 4 still used in a wide range of large corporations for their enterprise applications? Because it doesn't change. Because deploying a new version of an application takes months. And a new application takes years.
When you run true "enterprise applications" (I don't really like that term myself though) stability is paramount and ONLY surpassed in importance by "staticness" (don't know if that's a real word...). You don't want things to change. You don't even want a point release of some software you depend on because testing is expensive and takes a long time.
If you are one of the 3 guys in the IT department in a small company where you can whip up a new PHP app in a matter of hours, then the latest software is good. But as things get bigger, you want as much as possible to not change.
So yes, Debian stable is great for the enterprise. For the same reason(s) that Windows NT 4 is.
> And now it is my turn to disagree. When you start talking about the enterprise, a whole different set of rules come in to play.
Yes, but you are confusing to different situations: running an old server with Debian Woody, and installing a new server with Debian Woody. Since servers have a (hardware) lifetime of about 5 years, it makes a lot of sense to run the same software release on it for this time. You might do a mayor update if you need to, but usually you would just do security fixes. That's why you see lots of RedHat 8, Solaris 5.6 or Windown NT 4 around.
However, for new machines the picture is completely different. Getting hardware that runs NT 4 is nearly impossible, which is why every enterprise that does not have a clear migration strategy by now has a serious problem. Debian Woody is similar: finding a recent machine where you can install Woody is probably a challenge (think graphics card on the desktop, and gigabit ethernet/RAID/SATA on the server side).
So Debian is fine for machines that you installed 2 or 3 years ago, but it is not at all a possible choice for a new machine. Which, incidentally, completely defeats the purpose of stability.
It can't be the last -- we still have to wait for the dupe to get posted :P
I mod down anyone who says "I will be modded down for this", regardless of the rest of their comment