Toshiro wrote:
On a personal note, I like the debian "Release When it is Ready"
(RWR) policy. It stresses the point that sarge is ready. I dont want
to put pressure on developers and make a crappy release. I want a
something that "works". That is the real core competency of Debian -
"It works"!
Well, my point of view is that this obsession to get a 'perfect' release
causes more harm to Debian than anything else; everybody knows that
sarge as
it is today is much more stable than many distros out there, what are we
waiting for? It's ok to thoroughly test a new distro before it's
released,
but taking years to do so??? Come on!
We are waiting for two very important things.
1) buildds. AIUI, the current buildd situation is in a bit of
disarray since some b0rked xfree86 uploads caused corrupted
chroots on certain architectures. The problem is that the
architectures on which this occurred have very few package
autobuilders (I think s390 is one) and this caused pretty
much every package in the queue after the buggy uploads to
get stuck waiting. Thus, many packages are queued up for
Sarge, but have not yet been built for every architecture.
2) security team support. The #1 (potential) show stopper to a
release is security support. Naturally, the situation with
the autobuilders does not help, until this support is functioning
properly, release will be a way off.
That being said, I think I remember seeing something on -devel that
indicated that the last debian-installer RC was about to release with
a final push for bug fixes in it. Once that is done, and security
support is finalized, Sarge will be ready to go.
Besides, what about the people new to linux? Do you think anyone
would choose
to try a distro with obsolete software?
They can use Sarge. Seriously, if someone is new to Linux, they will
more than likely not be putting a server into production. Thus, Sarge
would more than adequately meet their stability needs.