[Buildroot] [git commit] website/lts: update release wording

commit: https://gitlab.com/buildroot.org/buildroot/-/commit/087a15f578823206ead71b791ea4d299af96ed38
branch: https://gitlab.com/buildroot.org/buildroot/-/tree/master

Update the release wording to align with the documentation.

Signed-off-by: Thomas Perale <[email protected]>
Signed-off-by: Thomas Petazzoni <[email protected]>
---
 docs/website/lts.html | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/docs/website/lts.html b/docs/website/lts.html
index 8384d3a88b..caa9344f4a 100644
--- a/docs/website/lts.html
+++ b/docs/website/lts.html
@@ -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/>
@@ -328,7 +328,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>
_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot