From: Michael Opdenacker <michael.opdenacker@rootcommit.com>
To: Antonin Godard <antonin.godard@bootlin.com>, docs@lists.yoctoproject.org
Cc: michael.opdenacker@rootcommit.com,
Quentin Schulz <quentin.schulz@cherry.de>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH v2 2/2] ref-manual: release-process: refresh the current LTS releases
Date: Tue, 22 Oct 2024 16:17:49 +0000 (UTC) [thread overview]
Message-ID: <36a47a8c-49e4-4881-b1f4-a20422260086@rootcommit.com> (raw)
In-Reply-To: <20241022-update-releases-svg-v2-2-6e7740f9a41c@bootlin.com>
Hi Antonin,
On 10/22/24 13:03, Antonin Godard wrote:
> Mention that Scarthgap the latest LTS in a bullet list next to
> Kirkstone. Reword the parapraph a bit to make it clearer after this
> change.
>
> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
> ---
> documentation/ref-manual/release-process.rst | 15 +++++++++------
> 1 file changed, 9 insertions(+), 6 deletions(-)
>
> diff --git a/documentation/ref-manual/release-process.rst b/documentation/ref-manual/release-process.rst
> index 920794679d2256cf0f8e9677c7739e5540c4bdd4..75532addbdcd52cb0ab13ee8ffd57a70e1fc8045 100644
> --- a/documentation/ref-manual/release-process.rst
> +++ b/documentation/ref-manual/release-process.rst
> @@ -103,13 +103,16 @@ have reached their End of Life (EOL) won't receive such updates.
>
> This started with version 3.1 ("Dunfell"), released in April 2020, which
> the project initially committed to supporting for two years, but this duration
> -was later extended to four years. Similarly, the following :term:`LTS` release,
> -version 4.0 ("Kirkstone"), was released two years later in May 2022 and the
> -project committed to supporting it for four years too.
> +was later extended to four years.
>
> -Therefore, a new :term:`LTS` release is made every two years and is supported
> -for four years. This offers more stability to project users and leaves more
> -time to upgrade to the following :term:`LTS` release.
> +A new :term:`LTS` release is made every two years and is supported for four
> +years. This offers more stability to project users and leaves more time to
> +upgrade to the following :term:`LTS` release.
> +
> +The currently supported :term:`LTS` releases are:
> +
> +- Version 5.0 ("Scarthgap"), released in April 2024 and supported until April 2028.
> +- Version 4.0 ("Kirkstone"), released in May 2022 and supported until May 2026.
>
> See :yocto_wiki:`/Stable_Release_and_LTS` for details about the management
> of stable and :term:`LTS` releases.
Looks good to me, thanks!
Reviewed-by: Michael Opdenacker <michael.opdenacker@rootcommit.com>
--
Michael Opdenacker
Root Commit
Embedded Linux Training and Consulting
https://rootcommit.com/
next prev parent reply other threads:[~2024-10-22 16:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 11:03 [PATCH v2 0/2] ref-manual: release process: update LTS section Antonin Godard
2024-10-22 11:03 ` [PATCH v2 1/2] ref-manual: release-process: update releases.svg Antonin Godard
2024-10-22 11:03 ` [PATCH v2 2/2] ref-manual: release-process: refresh the current LTS releases Antonin Godard
2024-10-22 16:17 ` Michael Opdenacker [this message]
2024-10-22 11:39 ` [PATCH v2 0/2] ref-manual: release process: update LTS section Antonin Godard
2024-10-22 16:13 ` Michael Opdenacker
2024-10-23 7:17 ` Antonin Godard
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=36a47a8c-49e4-4881-b1f4-a20422260086@rootcommit.com \
--to=michael.opdenacker@rootcommit.com \
--cc=antonin.godard@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=quentin.schulz@cherry.de \
--cc=thomas.petazzoni@bootlin.com \
/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.