* "C.M. Connelly" <cmc@debian.org> [2003-11-04 15:27]:
> One of the big things that people are looking for when considering
> alternatives is a distribution's security support policy
> (``errata'', in Red Hat's terminology) and information about the
> lifespan of a particular release, including, if possible, specific
> dates for a release's end-of-life.
Due to the nature of how Debian does its releases it can't be said how
long a specific release will be supported security-wise. For potato it
was supported for almost a year after woody was released. I don't know
how long it was done for slink, though.
I am not part of the security team but it definitely depends on too
much factors (like the results of the survey Joey usually starts after
some time the new release is done) to say that it will be supported for
so long or long. Especially noone can tell which lifespan a stable
release itself has because the new release will be done when its done.
Or, can _you_ tell when sarge will be ready? And when sarge+1 will come
out? How much architectures there will have to be supported (although
that is a rather minor factor due to the automatic build environment,
still a problem because they don't work like expected all the times)?
The information on the /releases/$CODENAME/ is too less for you, I
guess, right?
Sorry to not be of better help,
Alfie
--
I'd rather listen to Newton than to Mundie. He may have been dead for almost
three hundred years, but despite that he stinks up the room less.
-- Linus Torvalds
Attachment:
pgpi6sFDTd1kp.pgp
Description: PGP signature