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.'"
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."
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.
The Debian team will begin integrating X.Org into Unstable when Sarge is released. Except, they'll try and do it modularly, instead of monolithically...read more http://lists.debian.org/debian-x/2004/05/msg00431. html.
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.