Vanilla sources stabilization policy change

Summary

Team members working alongside upstream (and downstream) developer Greg k-h have decided to no longer request stabilization of the vanilla sources kernel. Team members and arch teams (understandably) are unable to keep up with the 1-2 weekly kernel releases (per version), and therefore will now direct users to always run the latest vanilla sources, or to run gentoo-sources for a fully Gentoo supported kernel. We will continue to do our best effort to request and get stabilized g-s versions.

Details

Some facts:

1. Upstream release rate is now a much higher 1-2 kernels a week.
2. Very frequently, these releases contain security fixes.
3. This rate of release puts arch teams in a difficult position, sinceĀ it is unsustainable to try to keep up to date with stabilization
4. By continuing the policy of providing a stable vanilla kernel version, Gentoo is giving a false sense of security to its users, since by the time the
kernel does get stabilized, a newer version with more security fixes is almost always already released

Eventually, we will be updating our project pages to reflect these changes.

3 Comments

  1. KevinTran

    Nice post

  2. Gerald

    If a kernel is marked stable by the kernel team there is no reason it should be marked unstable in gentoo. Marking a vanilla kernel unstable and then stable after two weeks is hypocritical.

    Make all non-rc vanilla kernel releases stable. Unless of course the ebuild has changed and could have introduced a bug, but that almost never seems to be the case for vanilla-sources.

  3. Ulf

    Please:
    Mark the latest stable kernels stable as they are released by greg and the others in ther slots,
    Mark all earlier versions of these stable kernels deprecated (unstable masked).
    Mark all other vanilla kernels unstable.
    This way if somebody wants to have a stable vanilla kernel he will get 3.10.10 when emerging vanilla-sources at the the time of this writing, and he can track this stable kernel.

Leave a Comment

Your email address will not be published. Required fields are marked *