[EMAIL PROTECTED] wrote: > In light of the perl issues (see my last message) and the message Linus > just sent off to linux-kernel about 2.1.125 and 2.2.0p1 could the freeze > be pushed back a week to see if we should QUICKLY re-target slink > towards 2.2.0?
No, this would hold the release for at least two more months.
. We have several kernel module package that need to be re-packaged.
. We have to rework on the sound modules, possibly, I dunno.
. We have to rework on the boot-floppies to cope with different
and/or more modules etc.
. We have to ensure that the new kernel headers won't infect
various compilation of programs.
. We might need to re-compile/re-package the libc.
. We need to include new programs / packages to interfere with
new kernel interfaces.
. We need to review our documentation wrt the kernel (maybe, I duno)
All this can't be done in 6 days.
Linux 2.2 is a good candidate for the next unstable to play with.
I believe that it will be fun, but I also forsee that there will
be problems.
I hope our release manager won't jump on that train too quick.
Regards,
Joey
--
No question is too silly to ask, but, of course, some are too silly
to answer. -- Perl book
pgpCyzcO0yeu8.pgp
Description: PGP signature
