Skip to contentSkip to conversation

docs/website: link LTS tooling documentation and staging branch

PATCH Applied Thomas Perale via buildroot 2 participants 6 messages Aug 11 – Aug 24

lore
Share & tools
lore
#0 lore raw

PATCH v3 1/1 docs/website: link LTS tooling documentation and staging branch

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.

---
v1 -> v2: took into account review from https://lore.kernel.org/r/[email protected]
v2 -> v3: took into account review from https://lore.kernel.org/r/[email protected]

---
 docs/website/lts.html | 40 ++++++++++++++++++++++++++--------------
 1 file changed, 26 insertions(+), 14 deletions(-)
docs/website/lts.html +26 -14
index 3bfd2a4374..8384d3a88b 100644
@@ -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>
 
Signature · 6 lines
2.55.0

_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot
author Reviewed-by Quentin Schulz on v3 1/1
#1 lore raw

Hi Thomas,

Quoted 9 lines · Thomas Perale

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.

Thanks!
Quentin
_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot

#2 lore raw

In reply of:

Quoted 6 lines

Hi Thomas,

Quoted 3 lines · Thomas Perale

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

Quoted 1 line

Those changes clearly explain the location and convention of the staging

Quoted 8 lines
Quoted 4 lines

branches and also link to more documentation on how to read the annotations.

Quoted 1 line

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

Thanks!
Quentin

Thanks for all the reviews !

Quoted 4 lines

_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot

_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot

#3 lore raw
In reply to Thomas Perale via buildroot
Quoted 9 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Thomas" == Thomas Perale via buildroot <[email protected]> writes:

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.

Quoted 6 lines

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

---
v1 -> v2: took into account review from https://lore.kernel.org/r/[email protected]
v2 -> v3: took into account review from https://lore.kernel.org/r/[email protected]

Committed, thanks.

Signature · 5 lines
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot
#4 lore raw
In reply to Thomas Perale via buildroot

Hello,

Quoted 10 lines · Thomas Perale via buildroot

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.

Thanks, applied to master!

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
#5 lore raw
Quoted 10 lines · Thomas Petazzoni

Hello,

Quoted 7 lines · Thomas Perale via buildroot

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.

Quoted 5 lines
Quoted 3 lines

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

Thanks, applied to master!

Dammit no, scratch that. This is not the patch from you that I applied, sorry about that.

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