Yocto Project Documentation
 help / color / mirror / Atom feed
From: Antonin Godard <antonin.godard@bootlin.com>
To: docs@lists.yoctoproject.org
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	 Antonin Godard <antonin.godard@bootlin.com>
Subject: [PATCH 1/3] poky.yaml.in: add DISTRO_RELEASE_SERIES
Date: Thu, 27 Nov 2025 17:37:45 +0100	[thread overview]
Message-ID: <20251127-bitbake-setup-updates-v1-1-75ac1e490a40@bootlin.com> (raw)
In-Reply-To: <20251127-bitbake-setup-updates-v1-0-75ac1e490a40@bootlin.com>

The DISTRO_RELEASE_SERIES represents the release series in numerical
format. So for whinlatter, it will always equal "5.3", no matter what
the latest tag or patch version is.

Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
---
 documentation/poky.yaml.in    | 2 ++
 documentation/set_versions.py | 1 +
 2 files changed, 3 insertions(+)

diff --git a/documentation/poky.yaml.in b/documentation/poky.yaml.in
index 7a19545d1..810efd4d5 100644
--- a/documentation/poky.yaml.in
+++ b/documentation/poky.yaml.in
@@ -11,6 +11,8 @@ DISTRO : "5.2"
 # represent the latest HEAD revision on the branch). DISTRO_LATEST_TAG should
 # always point to an existing tag.
 DISTRO_LATEST_TAG : "5.2"
+# The DISTRO_RELEASE_SERIES omits the patch version (so always X.Y).
+DISTRO_RELEASE_SERIES : "5.2"
 DISTRO_NAME_NO_CAP : "walnascar"
 DISTRO_NAME : "Walnascar"
 DISTRO_NAME_NO_CAP_MINUS_ONE : "styhead"
diff --git a/documentation/set_versions.py b/documentation/set_versions.py
index be05ef323..d146f93bb 100755
--- a/documentation/set_versions.py
+++ b/documentation/set_versions.py
@@ -190,6 +190,7 @@ print("Release series calculated to be %s" % ourseries)
 replacements = {
     "DISTRO" : ourversion,
     "DISTRO_LATEST_TAG": latesttag,
+    "DISTRO_RELEASE_SERIES": release_series[ourseries],
     "DISTRO_NAME_NO_CAP" : ourseries,
     "DISTRO_NAME" : ourseries.capitalize(),
     "DISTRO_NAME_NO_CAP_MINUS_ONE" : previousseries[0],

-- 
2.51.0



  reply	other threads:[~2025-11-27 16:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-27 16:37 [PATCH 0/3] bitbake-setup updates Antonin Godard
2025-11-27 16:37 ` Antonin Godard [this message]
2025-11-27 16:37 ` [PATCH 2/3] brief-yoctoprojectqs/index.rst: update available bitbake-setup configurations Antonin Godard
2025-11-27 16:37 ` [PATCH 3/3] brief-yoctoprojectqs/index.rst: switch shell block to to console lexer Antonin Godard
2025-11-27 16:47   ` [docs] " Quentin Schulz
2025-11-28 13:11     ` Antonin Godard
2025-11-28 13:14       ` Antonin Godard
2025-11-28 13:30       ` Quentin Schulz
2025-11-28 13:46         ` Antonin Godard
2025-12-01  8:35 ` [PATCH 0/3] bitbake-setup updates Antonin Godard

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=20251127-bitbake-setup-updates-v1-1-75ac1e490a40@bootlin.com \
    --to=antonin.godard@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=thomas.petazzoni@bootlin.com \
    /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