Linux Documentation
 help / color / mirror / Atom feed
From: Nick Desaulniers <ndesaulniers@google.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	stable@vger.kernel.org, Ben Hutchings <ben@decadent.org.uk>,
	Sasha Levin <sashal@kernel.org>,
	Nick Desaulniers <ndesaulniers@google.com>,
	Tyler Hicks <code@tyhicks.com>,
	Bagas Sanjaya <bagasdotme@gmail.com>
Subject: [PATCH v2] Documentation: process: replace outdated LTS table w/ link
Date: Fri, 14 Oct 2022 10:10:40 -0700	[thread overview]
Message-ID: <20221014171040.849726-1-ndesaulniers@google.com> (raw)
In-Reply-To: <Y0mSVQCQer7fEKgu@kroah.com>

The existing table was a bit outdated.

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.

Rather than keep this table updated, it does duplicate information from
multiple kernel.org pages. Make one less duplication site that needs to
be updated and simply refer to the kernel.org page on releases.

Suggested-by: Tyler Hicks <code@tyhicks.com>
Suggested-by: Bagas Sanjaya <bagasdotme@gmail.com>
Signed-off-by: Nick Desaulniers <ndesaulniers@google.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
Changes v1 -> v2:
* Rather than update table, use a link as per Tyler and Bagas.
* Carry forward GKH's SB tag.

 Documentation/process/2.Process.rst | 15 ++++-----------
 1 file changed, 4 insertions(+), 11 deletions(-)

diff --git a/Documentation/process/2.Process.rst b/Documentation/process/2.Process.rst
index e05fb1b8f8b6..6a919cffcbfd 100644
--- a/Documentation/process/2.Process.rst
+++ b/Documentation/process/2.Process.rst
@@ -126,17 +126,10 @@ than one development cycle past their initial release. So, for example, the
 5.2.21 was the final stable update of the 5.2 release.
 
 Some kernels are designated "long term" kernels; they will receive support
-for a longer period.  As of this writing, the current long term kernels
-and their maintainers are:
-
-	======  ================================	=======================
-	3.16	Ben Hutchings				(very long-term kernel)
-	4.4	Greg Kroah-Hartman & Sasha Levin	(very long-term kernel)
-	4.9	Greg Kroah-Hartman & Sasha Levin
-	4.14	Greg Kroah-Hartman & Sasha Levin
-	4.19	Greg Kroah-Hartman & Sasha Levin
-	5.4	Greg Kroah-Hartman & Sasha Levin
-	======  ================================	=======================
+for a longer period.  Please refer to the following link for the list of active
+long term kernel versions and their maintainers:
+
+	https://www.kernel.org/category/releases.html
 
 The selection of a kernel for long-term support is purely a matter of a
 maintainer having the need and the time to maintain that release.  There

base-commit: 9c9155a3509a2ebdb06d77c7a621e9685c802eac
-- 
2.38.0.413.g74048e4d9e-goog


  reply	other threads:[~2022-10-14 17:11 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
2022-10-14 16:46       ` Greg Kroah-Hartman
2022-10-14 17:10         ` Nick Desaulniers [this message]
2022-10-14 17:13           ` [PATCH v2] Documentation: process: replace outdated LTS table w/ link 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=20221014171040.849726-1-ndesaulniers@google.com \
    --to=ndesaulniers@google.com \
    --cc=bagasdotme@gmail.com \
    --cc=ben@decadent.org.uk \
    --cc=code@tyhicks.com \
    --cc=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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