[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y0mSVQCQer7fEKgu@kroah.com>
Date: Fri, 14 Oct 2022 18:46:13 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Tyler Hicks <code@...icks.com>
Cc: Bagas Sanjaya <bagasdotme@...il.com>,
Nick Desaulniers <ndesaulniers@...gle.com>,
Jonathan Corbet <corbet@....net>, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, stable@...r.kernel.org,
Ben Hutchings <ben@...adent.org.uk>,
Sasha Levin <sashal@...nel.org>
Subject: Re: [PATCH] Documentation: process: update the list of current LTS
On Fri, Oct 14, 2022 at 11:34:26AM -0500, Tyler Hicks wrote:
> On 2022-10-14 09:08:10, Greg Kroah-Hartman wrote:
> > On Fri, Oct 14, 2022 at 09:24:11AM +0700, Bagas Sanjaya wrote:
> > > On 10/14/22 01:34, Nick Desaulniers wrote:
> > > > 3.16 was EOL in 2020.
> > > > 4.4 was EOL in 2022.
> > > >
> > > > 5.10 is new in 2020.
> > > > 5.15 is new in 2021.
> > > >
> > > > We'll see if 6.1 becomes LTS in 2022.
> > > >
> > >
> > > I think the table should be keep updated whenever new LTS is announced
> > > and oldest LTS become EOL, to be on par with kernel.org homepage.
> >
> > Yeah, I didn't even realize this was in the kernel tree, I've just been
> > keeping kernel.org up to date.
>
> How about simply replacing this table with a pointer to
> https://www.kernel.org/category/releases.html so that you don't have to
> remember to update tables in two different places? It also has the
> benefit that the documentation is never stale (missing new LTS
> releases), even when someone is reading the documentation from an older
> kernel release.
Sure, that makes more sense!
greg k-h
Powered by blists - more mailing lists