From: Fiona Klute via buildroot <buildroot@buildroot.org>
To: Thomas Perale <thomas.perale@mind.be>, buildroot@buildroot.org
Cc: Titouan Christophe <titouan.christophe@mind.be>,
Edgar Bonet <bonet@grenoble.cnrs.fr>
Subject: Re: [Buildroot] [PATCH v2] docs/manual: update 'releases' to reflect LTS changes
Date: Mon, 27 Jul 2026 15:05:35 +0200 [thread overview]
Message-ID: <393511ee-1b43-4e3c-bc64-e71c1d900c0a@gmx.de> (raw)
In-Reply-To: <20260727125510.381611-1-thomas.perale@mind.be>
Hi Thomas!
Am 27.07.26 um 14:55 schrieb Thomas Perale:
> With the release of 2025.02, LTS releases are now made every two years
> with a 3-year support.
>
> This reflect the table showed at https://lts.buildroot.org/#releases.
>
> Signed-off-by: Thomas Perale <thomas.perale@mind.be>
> ---
> docs/manual/release-engineering.adoc | 22 ++++++++++++----------
> 1 file changed, 12 insertions(+), 10 deletions(-)
>
> diff --git a/docs/manual/release-engineering.adoc b/docs/manual/release-engineering.adoc
> index 0cf38183f9..ca64bd18b3 100644
> --- a/docs/manual/release-engineering.adoc
> +++ b/docs/manual/release-engineering.adoc
> @@ -5,19 +5,21 @@
> == Release Engineering
> === Releases
>
> -The Buildroot project makes quarterly releases with monthly bugfix
> -releases. The first release of each year is a long term support
> -release, LTS.
> +The Buildroot project makes quarterly releases with monthly bugfix releases.
> +Starting with 2025.02, the first release of every odd-numbered year is a long-term
> +support (LTS) release supported for three years.
>
> - - Quarterly releases: 2020.02, 2020.05, 2020.08, and 2020.11
> - - Bugfix releases: 2020.02.1, 2020.02.2, ...
> - - LTS releases: 2020.02, 2021.02, ...
> + - LTS releases: 2025.02, 2027.02, 2029.02 ...
> + - Stable releases: 2025.05, 2025.08, 2025.11, 2026.02, ...
> + - Bugfix releases: 2025.02.1, 2025.02.2, ...
>
> -Releases are supported until the first bugfix release of the next
> -release, e.g., 2020.05.x is EOL when 2020.08.1 is released.
> +LTS releases are supported for three years, with a one-year overlap with the
> +next LTS release, e.g., 2025.02.x is EOL when 2028.02 is released.
>
> -LTS releases are supported until the first bugfix release of the next
> -LTS, e.g., 2020.02.x is supported until 2021.02.1 is released.
> +Stable releases are supported until the next release, e.g., 2025.05.x is EOL
> +when 2025.08 is released.
I think "stable releases" is redundant and possibly confusing. All
releases are meant to be stable, the difference is support duration.
"Other releases" fits well in this context, in general "regular
releases" or "non-LTS releases" should be clearer.
Best regards,
Fiona
> +See the table at https://lts.buildroot.org/#releases[lts.buildroot.org].
>
> === Development
>
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-07-27 13:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-27 12:55 [Buildroot] [PATCH v2] docs/manual: update 'releases' to reflect LTS changes Thomas Perale via buildroot
2026-07-27 13:05 ` Fiona Klute via buildroot [this message]
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=393511ee-1b43-4e3c-bc64-e71c1d900c0a@gmx.de \
--to=buildroot@buildroot.org \
--cc=bonet@grenoble.cnrs.fr \
--cc=fiona.klute@gmx.de \
--cc=thomas.perale@mind.be \
--cc=titouan.christophe@mind.be \
/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