Re: [Openembedded-architecture] Yocto Project Release Tagging Changes

Marta Rybczynska <[email protected]> Tue, 31 Mar 2026 17:07:08 +0200
Newsgroups org.yoctoproject.lists.yocto
Message-ID <CAApg2=SVfBskC38U4206M84DB9B8DpcJFveU-PZzVFQA129X-g@mail.gmail.com>
On Fri, Mar 27, 2026 at 11:48 PM Michael Halstead via lists.openembedded.org
<[email protected]> wrote:

> Following discussions in the Yocto Project and OpenEmbedded TSCs we
> have begun standardizing git repository tags across the Yocto Project.
> This is being implemented to ensure consistency and simplify our
> automation around releases.
>
> Going forward, the following tagging standards will be enforced:
>
> Yocto Project Release Tags: All official Yocto Project release tags
> will consistently match the yocto-v.v.v format.
> Branch-Specific Tags: Tags that include the branch name (e.g.,
> kirkstone-4.0.34) that duplicate the official yocto-* tags will be
> removed from all repositories.
> Milestone Tags: Existing milestone tags will be replaced or converted
> to align with the new standard format, ensuring consistency with our
> versioning scheme. For example, 6.0_M2 will be replaced with
> yocto-6.0_M2.
>
> Please adjust any local scripts or workflows that rely on the older
> tag formats. Let me know if you have any questions or concerns
> regarding this change.
>
>
From the security perspective, removing existing tags isn't a wise
idea in case of forensics needs (need to figure out what was running
on a specific device).

Existing tags should stay for archive purposes.

Kind regards,
Marta