Yocto Project Discussions
 help / color / mirror / Atom feed
From: Michael Halstead <mhalstead@linuxfoundation.org>
To: yocto@lists.yoctoproject.org, yocto-patches@lists.yoctoproject.org
Cc: richard.purdie@linuxfoundation.org,
	Michael Halstead <mhalstead@linuxfoundation.org>
Subject: [yocto-autobuilder-helper][PATCH] scripts/release-parser: Update release generator for 5.1
Date: Sat, 13 Jul 2024 13:16:39 -0700	[thread overview]
Message-ID: <20240713201638.390039-2-mhalstead@linuxfoundation.org> (raw)

Comment out future stable branch for easy updating.

Signed-off-by: Michael Halstead <mhalstead@linuxfoundation.org>
---
 scripts/release-parser.py | 10 ++++++----
 1 file changed, 6 insertions(+), 4 deletions(-)

diff --git a/scripts/release-parser.py b/scripts/release-parser.py
index 7ae3c0b..0463667 100755
--- a/scripts/release-parser.py
+++ b/scripts/release-parser.py
@@ -84,8 +84,10 @@ def get_git_tags():
             status = "LTS until Apr. 2024"
         if branch == "yocto-4.0":
             status = "LTS until Apr. 2026"
-        if branch == "yocto-4.3":
-            status = "Stable Release"
+        if branch == "yocto-5.0":
+            status = "LTS until Apr. 2028"
+#        if branch == "yocto-5.1":
+#            status = "Stable Release"
 
         # Create a dictionary for the tag
         tag_dict = {
@@ -108,10 +110,10 @@ tags = sorted(get_git_tags(), key=lambda x: x["original_release_date"], reverse=
 
 tags.append(
     {
-        "series_version": "5.0",
+        "series_version": "5.1",
         "original_release_date": "",
         "latest_release_date": "",
-        "release_codename": "Scarthgap",
+        "release_codename": "Styhead",
         "latest_tag": "",
         "status": "Active Development",
         "download": "",
-- 
2.45.2



                 reply	other threads:[~2024-07-13 20:17 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=20240713201638.390039-2-mhalstead@linuxfoundation.org \
    --to=mhalstead@linuxfoundation.org \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=yocto-patches@lists.yoctoproject.org \
    --cc=yocto@lists.yoctoproject.org \
    /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