From: Willy Tarreau <w@1wt.eu>
To: Kaiwan N Billimoria <kaiwan.billimoria@gmail.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Reg the next LTS kernel (6.1?)
Date: Sat, 17 Dec 2022 17:40:59 +0100 [thread overview]
Message-ID: <20221217164059.GA4724@1wt.eu> (raw)
In-Reply-To: <CAPDLWs_GZaL7m2YqyfRgJE_s8RaQ4fyWbJKF8iDWzWJs84SJiQ@mail.gmail.com>
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.
Regards,
Willy
next prev parent reply other threads:[~2022-12-17 16:41 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-07 7:37 Reg the next LTS kernel (6.1?) Kaiwan N Billimoria
2022-10-07 7:46 ` Greg KH
2022-10-07 7:50 ` Kaiwan N Billimoria
2022-12-17 13:02 ` Kaiwan N Billimoria
2022-12-17 13:18 ` Greg KH
2022-12-17 13:44 ` Kaiwan N Billimoria
2022-12-17 16:40 ` Willy Tarreau [this message]
2022-12-20 1:45 ` Kaiwan N Billimoria
2022-12-18 8:42 ` Greg KH
2023-01-11 8:15 ` Conor Dooley
2023-01-11 11:33 ` Greg KH
2023-01-11 19:05 ` Conor Dooley
2023-01-12 12:23 ` Kris Chaplin
2023-01-12 12:26 ` Michal Simek
2023-01-13 11:27 ` Greg KH
2023-01-13 12:54 ` Michal Simek
2023-01-13 16:22 ` Greg KH
2023-01-13 21:40 ` Theodore Ts'o
2023-01-14 7:14 ` Willy Tarreau
2023-01-14 8:26 ` Greg KH
2023-01-14 8:47 ` Willy Tarreau
2023-02-05 6:27 ` Ruslan Bilovol
2023-02-16 10:41 ` Kris Chaplin
2023-02-16 11:20 ` Greg KH
2023-02-16 11:23 ` Kris Chaplin
2023-01-16 12:16 ` Michal Simek
2023-01-17 3:07 ` Theodore Ts'o
2023-01-16 12:02 ` Michal Simek
2023-01-13 11:24 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2022-10-07 15:04 Carl Dasantas
2022-10-07 15:36 ` Greg KH
2022-10-07 16:07 ` Carl Dasantas
2022-10-07 16:34 ` Greg KH
2022-10-07 19:50 ` Theodore Ts'o
2022-10-07 17:37 ` Slade Watkins
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221217164059.GA4724@1wt.eu \
--to=w@1wt.eu \
--cc=gregkh@linuxfoundation.org \
--cc=kaiwan.billimoria@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.