Anthony Towns <aj@azure.humbug.org.au> writes:
> don't want to wreck it for the people who're running critical
> things on unstable
IMHO that's an abuse of unstable - IMHO there should no critical
things running on unstable! And if someone is doing this, HE has to
ensure that nothing fails. Unstable is our experimental field and it
should/must be allowed to break things. Perhaps we should try to
release more up to date software or do it more often, so there is no
need at all to use unstable for any important thing other than
building and testing the next stable release.
The "Staging Areas" are good things, BUT IMHO they fix a symptom not
the problem. So let us fix the problem ...
Why shouldn't we start the next freeze two weeks after our slink
release!? There is much new software already in potato (Debian 2.2)
that is worth to be release soon. IMHO even the new kernel 2.2 and
glibc 2.1 can be moved on to be released later in Debian 2.4 if there
are any problems that can not be fixed in the two weeks period.
Bye
Christian
--
Dipl.-Ing. Christian Leutloff, Aachen, Germany leutloff@sundancer.oche.de
http://www.oche.de/~leutloff/ leutloff@debian.org
Debian GNU/Linux - http://www.de.debian.org/
Attachment:
pgplxM4VfNeev.pgp
Description: PGP signature