public inbox for docs@lists.yoctoproject.org
 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 v2 4/4] poky.yaml.in: split automatic and manually replaced macros
Date: Thu, 04 Dec 2025 14:36:41 +0100	[thread overview]
Message-ID: <20251204-release-updates-v2-4-04ca6c26ddd5@bootlin.com> (raw)
In-Reply-To: <20251204-release-updates-v2-0-04ca6c26ddd5@bootlin.com>

Instead of thinking some of these macros should be replaced when a new
release is out, split the variable that should be manually maintained
and the ones that are automatically computed in set_versions.py.

Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
---
 documentation/poky.yaml.in | 15 +++++++++++++--
 1 file changed, 13 insertions(+), 2 deletions(-)

diff --git a/documentation/poky.yaml.in b/documentation/poky.yaml.in
index 810efd4d5..56123495a 100644
--- a/documentation/poky.yaml.in
+++ b/documentation/poky.yaml.in
@@ -2,6 +2,12 @@
 # Macros used in the documentation
 #
 
+#
+# Automatically replaced by set_versions.py, no manual update required
+# Values below are placeholders to give an idea on how to use them in the
+# documentation.
+#
+
 # The DISTRO variable represents the current docs version. It should be used
 # when referring to the current docs version. See also DISTRO_LATEST_TAG.
 DISTRO : "5.2"
@@ -18,10 +24,15 @@ DISTRO_NAME : "Walnascar"
 DISTRO_NAME_NO_CAP_MINUS_ONE : "styhead"
 DISTRO_NAME_NO_CAP_LTS : "scarthgap"
 YOCTO_DOC_VERSION : "5.2"
-DISTRO_REL_TAG : "yocto-$DISTRO;"
-DISTRO_REL_LATEST_TAG : "yocto-&DISTRO_LATEST_TAG;"
 DOCCONF_VERSION : "dev"
 BITBAKE_SERIES : ""
+
+#
+# Not automatically replaced, manual updates required
+#
+
+DISTRO_REL_TAG : "yocto-$DISTRO;"
+DISTRO_REL_LATEST_TAG : "yocto-&DISTRO_LATEST_TAG;"
 YOCTO_DL_URL : "https://downloads.yoctoproject.org"
 YOCTO_RELEASE_DL_URL : "&YOCTO_DL_URL;/releases/yocto/yocto-&DISTRO;"
 MIN_PYTHON_VERSION : "3.9.0"

-- 
2.51.0



  parent reply	other threads:[~2025-12-04 13:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-04 13:36 [PATCH v2 0/4] Whinlatter release updates Antonin Godard
2025-12-04 13:36 ` [PATCH v2 1/4] ref-manual/svg/releases.svg: mark styhead and walnascar EOL Antonin Godard
2025-12-04 13:36 ` [PATCH v2 2/4] ref-manual/svg/releases.svg: mark whinlatter as current release Antonin Godard
2025-12-04 13:36 ` [PATCH v2 3/4] set_versions.py: add wrynose as devbranch Antonin Godard
2025-12-04 13:36 ` Antonin Godard [this message]
2025-12-16 16:12 ` [PATCH v2 0/4] Whinlatter release 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=20251204-release-updates-v2-4-04ca6c26ddd5@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