linux-kernel - Re: Reg the next LTS kernel (6.1?)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAPDLWs-3HiK_rNxfh=teQhGN2ZOaQE_NksKbzdRr3GcSBPJTfA@mail.gmail.com>
Date:   Tue, 20 Dec 2022 07:15:56 +0530
From:   Kaiwan N Billimoria <kaiwan.billimoria@...il.com>
To:     Willy Tarreau <w@....eu>
Cc:     Greg KH <gregkh@...uxfoundation.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Reg the next LTS kernel (6.1?)

On Sat, Dec 17, 2022 at 10:11 PM Willy Tarreau <w@....eu> wrote:
>
> On Sat, Dec 17, 2022 at 07:14:14PM +0530, Kaiwan N Billimoria wrote:
> > :-) Got it.
> > Taking your point into account, I'll rephrase: as the _convention_ is
> > to mark the last release in the year as LTS, is there any visibility
> > on when, or if, it comes about?
>
> What Greg tried to explain to you is that the convention is to pick a
> sufficiently well tested kernel to make sure its maintenance will not
> become a huge burden, and that it cannot be a single-person effort,
> testers are needed during that period. As such companies and/or users
> engaging in investing some resources for testing are extremely
> important and if some have a good reason to prefer investing that time
> on a different kernel, their choice will count more than just a kind
> request on the mailing list. Now you know how to make your voice count
> if you want/need 6.1 to become LTS.
>
Willy, Greg K-H, thanks for your guidance,
Kaiwan.
> Regards,
> Willy