From: Tyler Hicks <code@tyhicks.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Bagas Sanjaya <bagasdotme@gmail.com>,
Nick Desaulniers <ndesaulniers@google.com>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, Ben Hutchings <ben@decadent.org.uk>,
Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH] Documentation: process: update the list of current LTS
Date: Fri, 14 Oct 2022 11:34:26 -0500 [thread overview]
Message-ID: <20221014163426.tjxmek6xq6ojejea@sequoia> (raw)
In-Reply-To: <Y0kK2g+CUxbqPJ8d@kroah.com>
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.
Tyler
>
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2022-10-14 16:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 18:34 [PATCH] Documentation: process: update the list of current LTS Nick Desaulniers
2022-10-14 2:24 ` Bagas Sanjaya
2022-10-14 7:08 ` Greg Kroah-Hartman
2022-10-14 16:34 ` Tyler Hicks [this message]
2022-10-14 16:46 ` Greg Kroah-Hartman
2022-10-14 17:10 ` [PATCH v2] Documentation: process: replace outdated LTS table w/ link Nick Desaulniers
2022-10-14 17:13 ` Tyler Hicks
2022-10-14 17:41 ` Greg Kroah-Hartman
2022-10-15 2:06 ` Bagas Sanjaya
2022-10-18 0:04 ` Nick Desaulniers
2022-10-18 3:33 ` Bagas Sanjaya
2022-10-18 21:44 ` Jonathan Corbet
2022-10-22 3:27 ` Bagas Sanjaya
2022-10-14 7:08 ` [PATCH] Documentation: process: update the list of current LTS Greg Kroah-Hartman
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=20221014163426.tjxmek6xq6ojejea@sequoia \
--to=code@tyhicks.com \
--cc=bagasdotme@gmail.com \
--cc=ben@decadent.org.uk \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ndesaulniers@google.com \
--cc=sashal@kernel.org \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).