mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: "Ahmad Fatoum" <a.fatoum@pengutronix.de>,
	"Enrico Jörns" <ejo@pengutronix.de>
Subject: [PATCH] Documentation: security: mention long term stable release
Date: Mon, 10 Aug 2026 14:20:33 +0200	[thread overview]
Message-ID: <20260810122034.1966679-1-a.fatoum@pengutronix.de> (raw)

We occasionally backport changes to v2026.04.0, so adapt the README.rst
and SECURITY.md accordingly.

Reported-by: Enrico Jörns <ejo@pengutronix.de>
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
 README.rst  |  5 +++++
 SECURITY.md | 10 ++++++++--
 2 files changed, 13 insertions(+), 2 deletions(-)

diff --git a/README.rst b/README.rst
index 17bf288c4c60..71286904a866 100644
--- a/README.rst
+++ b/README.rst
@@ -273,6 +273,11 @@ are the release rules:
   We think that there is no need for pre releases, but if it's ever
   necessary, this is the scheme we follow.
 
+- Occasionally, a release may be designated a long term stable (LTS)
+  release and will continue to receive fixes for a longer period of
+  time. Refer to ``SECURITY.md`` in this directory to see, what
+  releases, besides the most recent, are actively maintained.
+
 - Only the monthly releases are archived on the web site. The tarballs
   are located in https://www.barebox.org/download/ and this location
   does never change, in order to make life easier for distribution
diff --git a/SECURITY.md b/SECURITY.md
index 9dd19d73d0aa..862dd14623d9 100644
--- a/SECURITY.md
+++ b/SECURITY.md
@@ -2,12 +2,18 @@
 
 ## Supported Versions
 
-The barebox project does not, at the moment, maintain any longer term
-support branches.
 Please update to new [barebox releases](https://github.com/barebox/barebox/releases)
 as they become available.
 Compatibility with old kernels is maintained over barebox releases.
 
+The [migration guides](https://www.barebox.org/doc/latest/migration-guides/index.html)
+can be helpful in adapting configuration to new releases.
+
+In addition, the barebox project currently maintains following long term stable (LTS)
+releases:
+
+  * [v2026.04.y](https://github.com/barebox/barebox/tree/stable/v2026.04)
+
 ## Reporting a Vulnerability
 
 Please report security vulnerabilities to security@barebox.org.
-- 
2.47.3




                 reply	other threads:[~2026-08-10 12:22 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20260810122034.1966679-1-a.fatoum@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=ejo@pengutronix.de \
    /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