From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Richard Purdie" <richard.purdie@linuxfoundation.org>,
<bitbake-devel@lists.openembedded.org>
Cc: "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
<docs@lists.yoctoproject.org>
Subject: Re: [bitbake-devel] [PATCH v2] doc: fix the switchers menu
Date: Wed, 04 Feb 2026 14:41:38 +0100 [thread overview]
Message-ID: <DG67YJ0354J5.3N96FN4DSMNML@bootlin.com> (raw)
In-Reply-To: <ad6217119fe0e7382684ef6a41078e172a4e8498.camel@linuxfoundation.org>
On Wed Feb 4, 2026 at 2:32 PM CET, Richard Purdie wrote:
> On Wed, 2026-02-04 at 11:03 +0100, Antonin Godard via lists.openembedded.org wrote:
>> Fix the switchers.js script of Bitbake to show what are the supported
>> versions and be able to switch between them.
>>
>> The default landing page is the stable branch and shows the BitBake
>> version along with the corresponding Yocto Project codename. This
>> hopefully makes it easier to remember the correspondance between the
>> BitBake version and the Yocto Project version.
>>
>> This works thanks to a set_versions.py script, which is largely inspired
>> from yocto-docs. It reads the tags from the repository and tries to
>> guess the currently checked out version of BitBake on which we are.
>>
>> The "obsolete" warning is now also shown when browsing outdated manuals,
>> meaning any version not part of activereleases in set_versions.py.
>>
>> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
>> ---
>> Note: This will be accompanied by a patch to adapt the Autobuilder to
>> generate this file for each release.
>> ---
>> Changes in v2:
>> - Remove environment information grabbing mechanism, making this fully
>> standalone.
>> - Link to v1: https://lore.kernel.org/r/20250915-fix-switchers-js-v1-0-523ef53fe802@bootlin.com
>> ---
>> doc/.gitignore | 2 +
>> doc/Makefile | 3 +-
>> doc/bitbake.yaml.in | 1 +
>
> I was about to merge this however is there a requirement to use yaml
> here? I ask mainly as we don't currently have yaml config files and I'd
> prefer not to start adding them and try to remain consistent with what
> we're using...
You're right, I don't see any obvious reason to use yaml either, and we could
use JSON instead. I just aligned with what was done on yocto-docs without this
afterthought. I'd be happy to make the switch (here and perhaps we could also do
that on yocto-docs). I'll try it out, thanks.
Antonin
next prev parent reply other threads:[~2026-02-04 13:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 10:03 [PATCH v2] doc: fix the switchers menu Antonin Godard
2026-02-04 13:32 ` [bitbake-devel] " Richard Purdie
2026-02-04 13:41 ` Antonin Godard [this message]
2026-02-04 15:01 ` [docs] " Quentin Schulz
2026-02-05 11:34 ` Antonin Godard
2026-02-05 13:08 ` Quentin Schulz
2026-02-05 13:40 ` Antonin Godard
2026-02-05 14:00 ` Quentin Schulz
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=DG67YJ0354J5.3N96FN4DSMNML@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=docs@lists.yoctoproject.org \
--cc=richard.purdie@linuxfoundation.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