mirror/buildroot
1
0
Fork 0
mirror of https://gitlab.com/buildroot.org/buildroot.git synced 2026-11-14 16:52:08 -10:00
Code Issues Packages Projects Releases Wiki Activity

docs/website: link LTS tooling documentation and staging branch

Browse Source 
Users asked where the notes are available and if the information are
publicly available.

Those changes clearly explain the location and convention of the staging
branches and also link to more documentation on how to read the
annotations.

Also update the timing of the different steps to be less specific.

Signed-off-by: Thomas Perale <thomas.perale@mind.be>
Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
This commit is contained in:
Thomas Perale
2026-08-11 15:43:12 +02:00
committed by Peter Korsgaard
parent 9f292bb7a1
commit 3e0d162011
1 changed files with 26 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

40
docs/website/lts.html
View File

@@ -46,7 +46,7 @@
<p class="br-lts-item-text">
Tracking of the vulnerabilities affecting Buildroot
is available at
<a href="https://security.buildroot.org/2025.02.x/vulnerability">security.buildroot.org</a>.
<a href="https://security.buildroot.org/">security.buildroot.org</a>.
<br/>
LTS stewards ensure this data remains up-to-date by actively
maintaining Buildroot packages metadata.
@@ -166,10 +166,6 @@
<br/>
<br/>
<p>
More details about the LTS workflow at <a href="https://gitlab.com/buildroot.org/buildroot-lts-tools">buildroot.org/buildroot-lts-tools</a>.
</p>
<div id="organization" class="br-lts-section-header">
<div class="br-lts-bg-grid"></div>
<div class="br-lts-title-box">How we work</div>
@@ -181,12 +177,28 @@
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
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
analyses updated.
</p>
<p>
Mid-week, the candidates are cherry-picked to a staging branch hosted on
<a href="https://gitlab.com/essensium-mind/buildroot/">gitlab.com/essensium-mind/buildroot</a>.
Every maintained branch has a staging branch, with the <code>.x</code>
suffix replaced by <code>.pre</code>. The staging branch allows other
maintainers to review the changes before they are pushed upstream.
</p>
<p>
By the end of the week, the staging branches are pushed upstream and
contributors are notified. Feedback from users, sponsors and
<a href="https://autobuild.buildroot.org/">autobuilders</a>
are then collected and
<a href="https://security.buildroot.org/">vulnerability analyses</a>
updated.
</p>
<p>
For more information about the development workflow, see the
<a href="https://gitlab.com/buildroot.org/buildroot-lts-tools/-/blob/main/tools/README.md">documentation</a>.
</p>
<br/>
@@ -222,13 +234,13 @@
</div>
<div class="br-lts-chart-row br-lts-chart-row--tall">
<div class="br-lts-chart-label">Sync with upstream branch</div>
<div class="br-lts-bar br-lts-col-start-9"></div>
<div class="br-lts-chart-label">Push to upstream branch</div>
<div class="br-lts-bar br-lts-bar--span-2 br-lts-col-start-9"></div>
</div>
<div class="br-lts-chart-row br-lts-chart-row--tall">
<div class="br-lts-chart-label">Update vulns</div>
<div class="br-lts-bar br-lts-col-start-10"></div>
<div class="br-lts-bar br-lts-bar--span-2 br-lts-col-start-10"></div>
</div>
</div>