Re: Kernel schedule proposal for Etch
Frederik Schueler <firstname.lastname@example.org> wrote:
> 15.09: upload 2.6.18 to unstable =20
>  The 2.6.18 release obviously depends on the upstream schedule, but 4
> weeks from now is realistic considering the 2.6.18-rc4 status.
Is is really mandatory to include the final 2.6.18 and not use 1.6.18-rc4-gkh?
instead if the schedule is too tight? That's still better than 2.6.17 and
important fixes from the final 2.6.18 can be cherry-picked with RM approval.