mirror/buildroot
1
0
Fork 0
mirror of https://gitlab.com/buildroot.org/buildroot.git synced 2026-08-01 21:23:51 -09:00
Code Issues Packages Projects Releases Wiki Activity

website/lts: fix typos

Browse Source 
Signed-off-by: Thomas Perale <thomas.perale@mind.be>
Signed-off-by: Julien Olivain <ju.o@free.fr>
This commit is contained in:
Thomas Perale
2026-03-19 16:02:46 +01:00
committed by Julien Olivain
parent e28b94d008
commit 50eca46e35
1 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
docs/website/lts.html
View File

@@ -29,7 +29,7 @@
3-year LTS support
</h2>
<p class="br-lts-item-text">
Starting with version <code>2025.02</code> the LTS support has been extended to
Starting with version <code>2025.02</code>, the LTS support has been extended to
<strong>3 years</strong>, replacing the previous 1-year cycle.
</p>
</div>
@@ -65,7 +65,7 @@
<p class="br-lts-item-text">
To ensure a consistent release cadence and maintenance
workflow, paid LTS stewards are assigned to the weekly LTS
maintainance tasks.
maintenance tasks.
</p>
</div>
</div>
@@ -96,7 +96,7 @@
The Buildroot LTS sponsorship initiative has evolved from a more
comprehensive understanding of the needs of our user base.
<br/>
To address these requirements the release model evolves into the following.
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.
@@ -177,12 +177,12 @@
</div>
<p>
Each week the LTS stewards defines the set of commits to
analyze based on the previous week commits to the master branch. The
Each week, the LTS stewards define the set of commits to
analyze based on the previous week's commits to the master branch. The
commits are then annotated to define a list of candidates for the LTS
branches.
<br><br>
On Thursday the candidates are cherry-picked to a staging branch to be
On Thursday, the candidates are cherry-picked to a staging branch to be
reviewed by the other maintainers. On Thursday evening the branch is
synced with upstream and contributors are notified. Feedback from
users, sponsors and autobuilders are then collected and vulnerability