From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Quentin Schulz" <quentin.schulz@cherry.de>,
<docs@lists.yoctoproject.org>
Cc: "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
Subject: Re: [docs] [PATCH 1/2] poky.yaml: introduce DISTRO_LATEST_TAG
Date: Tue, 13 May 2025 10:28:06 +0200 [thread overview]
Message-ID: <D9UW30Q030G2.22VWR1SASAWG8@bootlin.com> (raw)
In-Reply-To: <caeb301c-abfe-4220-b24b-1073f43efc3a@cherry.de>
On Wed Apr 23, 2025 at 11:56 AM CEST, Quentin Schulz wrote:
> Hi Antonin,
>
> On 4/23/25 11:33 AM, Antonin Godard wrote:
> [...]
>>> I don't think we should be using &DISTRO; anymore? Most of the time we
>>> don't want to be printing .999 on the landing page of
>>> docs.yoctoproject.org! For the dev page, that's different.
>>
>> I would like to agree, but at the same time, wouldn't it be confusing to have a
>> real tag (e.g. 5.1.8) when reading for the latest tip of the branch? It would be
>
> Does it matter? We should only be doing bug fixing and ideally without
> breaking backward compatibility in a given release branch.
> Again, the development (master) branch is a different story here.
>
>> somewhat accurate, but not _stricty_ accurate as to which version of the doc you
>> are actually reading (the latest tip).
>>
>
> The issue is that this tag simply doesn't exist so we should absolutely
> never use it when code is involved, as the instructions will simply not
> work.
Right, so the code parts of the docs should be adapted to use DISTRO_LATEST_TAG,
but I still think using DISTRO in the textual parts is useful to distinguish a
branch tip version of the docs and a tagged version of the docs.
>> I'm trying to think of a way to make it clear that 999 represent the branch's
>> tip.
>>
>
> I'm failing to see how it is relevant to the user that the docs are
> built from the branch's tip instead of the tag?
There might be a reason that goes beyond my work on the docs, but it is kind of
useful to me to monitor changes as we go, or just to provides up-to-date links
to people.
It is questionable that this should be the default landing page though.
> BTW, it seems like once you're on a tagged release, you cannot go back
> to the .999 from the dropdown menu, is that intended?
Sounds like a bug to me!
Thanks,
Antonin
--
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-05-13 8:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-09 9:55 [PATCH 0/2] Fix broken links when building on branch tip Antonin Godard
2025-04-09 9:55 ` [PATCH 1/2] poky.yaml: introduce DISTRO_LATEST_TAG Antonin Godard
2025-04-14 12:18 ` [docs] " Quentin Schulz
2025-04-16 7:46 ` Antonin Godard
2025-04-16 9:58 ` Quentin Schulz
2025-04-17 7:21 ` Antonin Godard
2025-04-18 11:28 ` Quentin Schulz
2025-04-23 9:33 ` Antonin Godard
2025-04-23 9:56 ` Quentin Schulz
2025-05-13 8:28 ` Antonin Godard [this message]
2025-05-15 7:50 ` Quentin Schulz
2025-05-22 9:51 ` Antonin Godard
2025-05-22 12:13 ` Quentin Schulz
2025-04-09 9:55 ` [PATCH 2/2] Fix dead links that use the DISTRO macro 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=D9UW30Q030G2.22VWR1SASAWG8@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox