All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Antonin Godard" <antonin.godard@bootlin.com>
To: <quentin.schulz@cherry.de>, <docs@lists.yoctoproject.org>
Cc: "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
Subject: Re: [docs] [PATCH v2 1/3] tools/fetch-releases-json: add to fetch and format releases.json
Date: Tue, 03 Mar 2026 14:14:04 +0100	[thread overview]
Message-ID: <DGT6A4L263BU.ODVFK33QLCYV@bootlin.com> (raw)
In-Reply-To: <38678bef-ba8f-4181-85f4-c367c3f6dc29@cherry.de>

Hi,

On Fri Feb 27, 2026 at 11:26 AM CET, Quentin Schulz via lists.yoctoproject.org wrote:
> Hi Antonin,
>
> On 2/26/26 3:00 PM, Antonin Godard via lists.yoctoproject.org wrote:
>> Add a simple script that can be used to fetch and format the
>> releases.json file from https://dashboard.yoctoproject.org/releases.json.
>> 
>
> OK but why do we want this in the tree? It'll still be regularly outdated.
>
> I understand not wanting to rely on a network connection, but we already 
> need that for the bitbake's object.inv we download... so this ain't that 
> much different.

You're right, I forgot about that inventory file :( made this change with an
offline build in mind.

Fetching the file when building seems like a proper solution, although:

- IMO, we need to fallback on fixed values, even if they're outdated, to not
  block a documentation build if we can't fetch the releases.json file

- on the Autobuilder, we need to do the opposite: block a build if we can't
  fetch the releases.json file

- avoid fetching the file again if we already did (especially important on the
  Autobuilder as we don't want the file to be fetched for every tag + we don't
  want it to change during a build)

With this in mind, I'll work on a v3. Thanks for your insights!

Antonin


  reply	other threads:[~2026-03-03 13:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-26 14:00 [PATCH v2 0/3] set_versions.py: build with versions from releases.json Antonin Godard
2026-02-26 14:00 ` [PATCH v2 1/3] tools/fetch-releases-json: add to fetch and format releases.json Antonin Godard
2026-02-26 15:37   ` Antonin Godard
2026-02-27 10:26   ` [docs] " Quentin Schulz
2026-03-03 13:14     ` Antonin Godard [this message]
2026-03-03 14:48       ` Quentin Schulz
2026-03-03 15:04         ` Antonin Godard
2026-02-26 14:00 ` [PATCH v2 2/3] set_versions.py: build with versions from releases.json Antonin Godard
2026-02-26 14:00 ` [PATCH v2 3/3] set_versions.py: make it possible to use a different releases.json file 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=DGT6A4L263BU.ODVFK33QLCYV@bootlin.com \
    --to=antonin.godard@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=quentin.schulz@cherry.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.