MIME-Version: 1.0
References: <CAPDLWs9KWKs_-fpAp2=97uBARYqrHSYTPEU6RbqtWjAD8NpqgQ@mail.gmail.com>
 <CAPDLWs9CoWw7NLfrtCfMsRAdCSfBgomVELRhM70QWVca99z65A@mail.gmail.com>
 <Y53BputYK+3djDME@kroah.com> <c6c4787f-f0c6-7285-f782-d36bd86b1e01@amd.com>
 <96e41e6d-bec9-f8cf-22ed-1fa5d9022238@amd.com> <Y8FAFAwB9gBzQXQG@kroah.com>
 <314489f6-cb54-fb3b-6557-d69b1284fa4d@amd.com> <Y8GFYEnIy0Wbh/n6@kroah.com>
 <Y8HPw2t+TbdXa83C@mit.edu> <20230114071412.GB5088@1wt.eu> <Y8JnHyKNTHMjsHSb@kroah.com>
In-Reply-To: <Y8JnHyKNTHMjsHSb@kroah.com>
From:   Ruslan Bilovol <ruslan.bilovol@gmail.com>
Date:   Sun, 5 Feb 2023 01:27:42 -0500
Message-ID: <CAB=otbS2uwfm0+YHMXXY3TM94V82LtxgcBXGZq1Zxbvd36Wkug@mail.gmail.com>
Subject: Re: Reg the next LTS kernel (6.1?)
To:     Greg KH <gregkh@linuxfoundation.org>
Cc:     Willy Tarreau <w@1wt.eu>, "Theodore Ts'o" <tytso@mit.edu>,
        Michal Simek <michal.simek@amd.com>,
        Kris Chaplin <kris.chaplin@amd.com>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Sat, Jan 14, 2023 at 3:31 AM Greg KH <gregkh@linuxfoundation.org> wrote:
>
> On Sat, Jan 14, 2023 at 08:14:12AM +0100, Willy Tarreau wrote:
> > On Fri, Jan 13, 2023 at 04:40:19PM -0500, Theodore Ts'o wrote:
> > > On Fri, Jan 13, 2023 at 05:22:56PM +0100, Greg KH wrote:
> > > > > I am just saying that developers/driver owners can simple do calculation to
> > > > > identify LTS version. When they know it they also know time when their
> > > > > deadline is for upstreaming work. It means if patch is accepted between
> > > > > 6.0-r1 and 6.0-rc5/6 they know that it will get to 6.1 merge window.
> > > >
> > > > That is what I am afraid of and if it causes problems I will purposfully
> > > > pick the previous release.  This has happened in the past and is never
> > > > an excuse to get anything merged.  Code gets merged when it is ready,
> > > > not based on a LTS release.
> > >
> > > This is probably the best reason not to preannounce when the LTS
> > > release will be ahead of time --- because it can be abused by
> > > developers who try to get not-ready-for-prime-time features into what
> > > they think will be the LTS kernel, with the result that the last
> > > release of the year could be utterly unsitable for that perpose.
> >
> > We know this risk exists but since Greg never makes promises on any
> > version, it remains reasonable.
>
> I have to _not_ make promises because in the past when I did, people
> threw crap into the kernel with the "justification" that they had to get
> it in this specific kernel because it was going to be the LTS one.
>
> We can't have nice things, because people abuse it :(

So, is there a final decision taken on what will be our next LTS?
Went through https://kernel.org/category/releases.html but it still shows
v5.15 as the latest LTS version.

Thanks,
Ruslan