website/lts: update release wording

Update the release wording to align with the documentation.

Signed-off-by: Thomas Perale <thomas.perale@mind.be>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
This commit is contained in:
Thomas Perale
2026-08-11 14:05:30 +02:00
committed by Thomas Petazzoni
parent 70f762ea6e
commit 087a15f578

View File

@@ -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>