Re: [docs] [PATCH 22/53] overview-manual/development-environment.rst: remove obsolete poky repo references

["Antonin Godard" <antonin.godard@bootlin.com>]

Hi,

On Mon Jan 26, 2026 at 4:18 PM CET, Quentin Schulz wrote:
> Hi Antonin,
>
> On 1/26/26 3:57 PM, Antonin Godard wrote:
>> Hi,
>> 
>> On Tue Jan 13, 2026 at 2:49 PM CET, Quentin Schulz wrote:
>> [...]
>>>> +      :term:`BitBake` repositories. For example, if you have checked out the "&DISTRO_NAME_NO_CAP;"
>>>
>>> Do not use this branch as it will never exist as it points to the name
>>> of the not-yet-released version. You want to use
>>> DISTRO_NAME_NO_CAP_MINUS_ONE likely (or DISTRO_NAME_NO_CAP_LTS).
>> 
>> No? This is true for the dev version of the docs, but once the docs are
>> released, this equals to the current version of the docs you are reading.
>> 
>> [...]
>>>>    It is important to understand that Git tracks content change and not
>>>>    files. Git uses "branches" to organize different development efforts.
>>>> -For example, the ``poky`` repository has several branches that include
>>>> +For example, the :yocto_git:`yocto-docs </yocto-docs>` repository has several branches that include
>>>>    the current "&DISTRO_NAME_NO_CAP;" branch, the "master" branch, and many
>>>
>>> DISTRO_NAME_NO_CAP is wrong here, it's the not-yet-released version. We
>>> shouldn't be using that (or set_versions.py doesn't work right now). Or
>>> is it just wrong for the "master" branch of the docs maybe? Still,
>>> people will likely reach the official docs through the master branch?
>>> Should we show a warning on the docs for the master branch stating this
>>> applies only to unreleased software?
>> 
>> No, docs.yoctoproject.org shows the latest released version of the docs, which
>> is the tip of the whinlatter branch right now. The master version of the docs is
>> docs.yoctoproject.org/dev, and the master-next version of the docs is
>> docs.yoctoproject.org/next.
>> 
>
> Ack. FYI, the version is invalid though, c.f. 
> https://docs.yoctoproject.org/ref-manual/system-requirements.html#supported-linux-distributions 
> search for 5.3.999. So we should be wary of using that.

Correct, I'm also not a fan of that and find it confusing (a lot of people do)…
At the same time I wonder what else we could do/show when we're pointing to a
branch tip.

"5.3.999" -> "5.3 (latest)"?

> All good, got confused, sorry for the noise.

No worries!

Antonin

-- 
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com