docs/manual: update 'releases' to reflect LTS changes
PATCH v3 1/1 docs/manual: update 'releases' to reflect LTS changes
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.
---
v1 --> v2: Took the suggestion from https://lore.kernel.org/r/<[email protected]>
v2 --> v3: Took the suggestion from https://lore.kernel.org/r/<[email protected]> . All the releases are stable and divided in two categories: LTS & non-LTS. Also updated the lts website page to reflect those changes.
--- docs/manual/release-engineering.adoc | 22 ++++++++++++---------- 1 file changed, 12 insertions(+), 10 deletions(-)
docs/manual/release-engineering.adoc +12 -10
@@ -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 stable 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 ... + - Non-LTS 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. +Non-LTS releases are supported until the next release, e.g., 2025.05.x is EOL +when 2025.08 is released. + +See the table at https://lts.buildroot.org/#releases[lts.buildroot.org]. === Development
Signature · 6 lines
2.55.0 _______________________________________________ buildroot mailing list [email protected] https://lists.buildroot.org/mailman/listinfo/buildroot
PATCH v3 1/1 website/lts: update release wording
Update the release wording to align with the documentation.
--- docs/website/lts.html | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-)
docs/website/lts.html +5 -5
@@ -80,7 +80,7 @@ </h2> <p class="br-lts-item-text"> Vulnerability fixes applied to the <code>master</code> branch will be - prioritized for backporting to the LTS & stable branches. + prioritized for backporting to stable branches. </p> </div> </div>
@@ -98,9 +98,9 @@ <br/> To address these requirements, the release model evolves into the following. <br/> - The LTS releases are now extended for a 3-year period. An LTS release - is started every 2 years. - In between, stable releases are made every 3 months. + Starting with 2025.02, the first release of every odd-numbered year is a long-term + support (LTS) release supported for three years. + In between, non-LTS releases are made every 3 months. </p> <br/>
@@ -316,7 +316,7 @@ To make sure the packages of interest to the sponsors don't include regressions between releases. Sponsors may submit a list of packages to be tested - before an LTS & stable release. + before a bugfix release. </p> </div> </div>
Signature · 6 lines
2.55.0 _______________________________________________ buildroot mailing list [email protected] https://lists.buildroot.org/mailman/listinfo/buildroot
Re: [Buildroot] [PATCH v3] website/lts: update release wording
Hello Thomas,
Quoted 3 lines · Thomas Perale via buildroot
Update the release wording to align with the documentation.
Signed-off-by Thomas Perale <[email protected]>
This is the patch that I applied to master, for real :-)
Thanks!
Thomas
Signature · 7 lines
Thomas Petazzoni, co-owner and CEO, Bootlin Embedded Linux and Kernel engineering and training https://bootlin.com _______________________________________________ buildroot mailing list [email protected] https://lists.buildroot.org/mailman/listinfo/buildroot
Thomas Petazzoni via buildroot
AppliedQuoted 6 lines · Thomas Perale via buildroot
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 <[email protected]>
Applied to master, thanks!
Thomas
Signature · 7 lines
Thomas Petazzoni, co-owner and CEO, Bootlin Embedded Linux and Kernel engineering and training https://bootlin.com _______________________________________________ buildroot mailing list [email protected] https://lists.buildroot.org/mailman/listinfo/buildroot
Thomas Perale via buildroot
AppliedIn reply of:
Quoted 6 lines
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 <[email protected]>
Applied to 2025.02.x & 2026.05.x. Thanks
Quoted 50 lines
---
v1 --> v2: Took the suggestion from https://lore.kernel.org/r/<[email protected]>
v2 --> v3: Took the suggestion from https://lore.kernel.org/r/<[email protected]> . All the releases are stable and divided in two categories: LTS & non-LTS. Also updated the lts website page to reflect those changes.--- docs/manual/release-engineering.adoc | 22 ++++++++++++---------- 1 file changed, 12 insertions(+), 10 deletions(-)docs/manual/release-engineering.adoc +12
-10@@ -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 stable 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 ... + - Non-LTS 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. +Non-LTS releases are supported until the next release, e.g., 2025.05.x is EOL +when 2025.08 is released. + +See the table at https://lts.buildroot.org/#releases[lts.buildroot.org]. === DevelopmentSignature · 6 lines
2.55.0 _______________________________________________ buildroot mailing list [email protected] https://lists.buildroot.org/mailman/listinfo/buildroot
_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot