Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Perale via buildroot <buildroot@buildroot.org>
To: buildroot@buildroot.org
Cc: Quentin Schulz <quentin.schulz@cherry.de>
Subject: [Buildroot] [PATCH v3] docs/website: link LTS tooling documentation and staging branch
Date: Tue, 11 Aug 2026 15:43:12 +0200	[thread overview]
Message-ID: <20260811134312.170306-1-thomas.perale@mind.be> (raw)

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>
---
v1 -> v2: took into account review from https://lore.kernel.org/r/f6b4e9a2-8ee5-4799-960f-36dbf5710da6@cherry.de
v2 -> v3: took into account review from https://lore.kernel.org/r/8d6fa46d-8200-454e-b5ac-aeccc4809647@cherry.de
---
 docs/website/lts.html | 40 ++++++++++++++++++++++++++--------------
 1 file changed, 26 insertions(+), 14 deletions(-)

diff --git a/docs/website/lts.html b/docs/website/lts.html
index 3bfd2a4374..8384d3a88b 100644
--- a/docs/website/lts.html
+++ b/docs/website/lts.html
@@ -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>
 
-- 
2.55.0

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2026-08-11 13:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-11 13:43 Thomas Perale via buildroot [this message]
2026-08-11 14:01 ` [Buildroot] [PATCH v3] docs/website: link LTS tooling documentation and staging branch Quentin Schulz via buildroot
2026-08-11 14:07   ` Thomas Perale via buildroot
2026-08-23 19:46 ` Peter Korsgaard
2026-08-24 19:18 ` Thomas Petazzoni via buildroot
2026-08-24 19:18   ` Thomas Petazzoni via buildroot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260811134312.170306-1-thomas.perale@mind.be \
    --to=buildroot@buildroot.org \
    --cc=quentin.schulz@cherry.de \
    --cc=thomas.perale@mind.be \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox