Slashdot Mirror
Debian Announces Sarge Will Include GNOME 2.8
El Cubano writes "A recent posting to the debian-devel-announce mailing list announces that Sarge will release with GNOME 2.8. From the announcement: 'After requests and a detailed proposal from the GNOME team, we accepted
an upload of GNOME 2.8 into sid, and, via the usual mechanisms, into
sarge. We should mention that the release team was running out of
objections to GNOME 2.8 in unstable that the GNOME team hasn't
satisfactorily addressed; this, and the fact that they have demonstrated
good reaction times of late are the main reasons why we're approving it
despite the timing.'"
And its scheduled for release at roughly the same time as Saddam Hussein
Athletic Scholarships to universities make as much sense as academic scholarships to sports teams.
Debian incorporating newly released software into stable in less than two years, who would of though.
Not all conservatives are stupid,
but it is true that most stupid people are conservative.
- Hume
Actualy reading the announcement would have answered your question: "In the meantime, we were also asked why we decided to go with KDE 3.2, and if it would be possible to go with KDE 3.3 instead. The main reason is that KDE 3.3 in unstable started with some RC bugs, and there was no proposal from the KDE team how to proceed. The door is only closed, but not locked for KDE 3.3. We are still open for proposals how to sort the KDE 3.3 issues out, and there has been some productive discussion of late about that - but no final decision yet."
Garden Gnome 1.0 is scheduled for release on my lawn this spring...
Luke: What is it Obi-Wan ?
OWK: I felt a deep disturbance in the force. It was as if Debian decided to be more current with their packages.
I've been running stable (woody) since it came out, and it has served me well. I started using Adrian Bunk's backports, and then selected things from backports.org... Then I upgraded to KDE from downloads.kde.org, and then openoffice from some other backport collection. Amazingly enough, this collection of software worked well enough for me.
I recently took the plunge and converted a couple of machines to testing (soon to be sarge). First thing I will say is that even with all of the backports, the upgrade went very smoothly. And I'll also say that sarge is working well for me; so well that I've installed it on several other machines using the new debian-installer rc candidates, and that has worked flawlessly for me as well!
As soon as security update support is up and running for testing, anyone remotely interested in sarge should consider upgrading and filing bug reports as appropriate. This is how you can help speed up the "real" release of sarge!
And I do think that when sarge comes out, it's going to be an excellent platform. It is so much nicer about hardware autodetection, font handling, and about a million other things... Without losing any of the old things that you love about Debian.
Lets hope that the next stable release doesn't take too long, although given Debian's nature, it's hard to see how it won't... Assuming the official compiler moves to gcc 3.4 (or the upcoming 4.0), then there is going to be another painful transition for all of those C++ applications. Hopefully someday g++ will have a stable C++ ABI and those transitions won't be an issue for projects shipping C++ libraries... (This was one of the major issues for getting KDE into unstable earlier this year.)
Situation now:
potato = obselete
woody = stable
sid = unstable
sarge = testing
Once sarge is declared stable,
woody = obselete
sid = unstable
sarge = stable
unknown = testing
So, sid will remain unstable and a new name for the testing branch will have to be decided (unless I missed something and that's already happened).
anyone know whether x.org will make it into sarge as well?
my blog
is Sarge Will someone I should know? I am familiar with General Failure, though.
-- Make America hate again!
And for most users, at any one point in time the Unstable one offers the best tradeoff between features and stability. The current situation is that Sid is unstable, Sarge is testing and Woody is Stable.
Real Soon Now, they'll all shuffle along one, Woody will die and Sarge will become stable. I run sarge on my home and work machines and it's completely rock solid.
unstable will always be called sid. i.e.:
stable -> slink
testing -> potato
unstable -> sid
stable ->potato
testing -> woody
unstable ->sid
stable ->woody
testing -> sarge
unstable ->sid
stable ->sarge
testing -> etch
unstable -> sid
sid never changes.
KDE 3.3.1 is stable enough to where I'm relying on it on my ThinkPad. Sid is your friend. Gotta love the improved Konqui.
Oh yeah, and KDE has none of these problems that people are reporting with GNOME. Snappy performance on a Pentium II Mobile 400MHz. I daresay even snappier than the install of Windows 2000 SP4 on the other partition.
There is no reason why people running personal Debian desktop systems shouldn't liberally add Sid packages to their system. What Debian.Org calls "unstable" is actually ready for prime time on non-critical machines.
If you run a critical server, go with Woody aka Stable. If you can live a little on the edge with your server, run Sarge/Testing/Release Candidate. If you are setting up a desktop for Grandma, use Sarge with no Sid packages. For everyone else, live on the edge, baby! ^_^
Knowledge is power. Knowledge shared is power multiplied.