[lkml]   [2005]   [Mar]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: RFD: Kernel release numbering
    A couple of weeks ago I was at LinuxWorldExpo in Boston and was talking
    to several people about the stability of the 2.6 kernel. Every one I
    talked to seemed to be nervous about using it. Some did, and some did
    not and stayed with 2.4. But each one had a different level of faith in
    which kernel to use. The biggest complaint seems that 2.6 had taken up
    the MS SP approach to patches. This patch fixes foo bug but with bar
    feature added, could introduce foo2 bug. So those I talked to really
    wanted a point where only fixes to real bugs were added with no extra

    Although it looks like Linus has decided to go with the 2.6.x.y scheme,
    I would like to say that it seems to be the perfect solution to those
    that I talked to. If Linus wants to get as many people to test the
    lastest kernel, then this may help in that aspect. Some would choose the
    2.6.x.0, with the excitement of the latest (but not so stable) kernel,
    others may wait till 2.6.x.>5, or some other number, or more likely,
    after some specified time frame. But this allows different people to
    start testing the latest kernel when they feel comfortable with it.

    I would even recommend that the 2.6.x.0 be equivalent to the -rc2
    kernel. So if there's some feature that you would like, in 2.6.x,
    instead of asking for someone to back port it, you could just wait for
    2.6.x.y where y is something you are comfortable with. I'm sure people
    will still ask, but the rule would be to tell them NO.

    The problem with 2.4 / 2.5 was that there were features in 2.5 that
    people would want in 2.4 but couldn't wait a year for them. This method
    would allow that time to be shortened and new features won't take
    forever to get to a stable release.

    So kudos to Greg. I hope that everyone supports his efforts and fights
    against anyone that suggests a non essential bug fix to go into a
    2.6.x.y branch.

    I know lots of people (including myself) that only use the vanilla
    kernel, and never the kernel that comes from the distributor. So I hope
    this helps us. Unfortunately, I have a NVidia card, which seldom works
    with the latest kernels, so I don't get to test as often as I would
    like, unless I sacrifice 3D graphics.


    -- Steve

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 14:10    [W:0.022 / U:17.848 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site