> -----Original Message----- > From: [email protected] <openembedded- > [email protected]> On Behalf Of Michael Halstead via > lists.openembedded.org > Sent: den 27 mars 2026 23:48 > To: openembedded-architecture <openembedded- > [email protected]>; Yocto-mailing-list > <[email protected]> > Cc: Lee, Chee Yang <[email protected]> > Subject: [Openembedded-architecture] Yocto Project Release Tagging Changes > > 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.
Does that mean the next release will be yocto-6.0.0, rather than the expected yocto-6.0 (as previous major releases have been named)? If so, I'm all for it. > 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. NO! ABSOLUTELY NOT! Removing official release tags is a way, way worse idea than, e.g., removing the master branch when starting to use main. All our manifests for releases using the poky repository use these tags to fetch and then use the SHA-1 to verify consistency, much like how bitbake recipes do nowadays. Removing these tags will break those manifests, making it a lot more cumbersome when one has to go back and build an old release. > 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. > > Thank you, > > -- > Michael Halstead > Linux Foundation / Yocto Project > Staff IT Engineer It is fine to use the new schemes for new tags going forward, but you really should not consider removing existing official release tags. Yes, it means there will be an inconsistency with the past history, but that is the way things were then. Do not try to retrofit it. //Peter
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#2313): https://lists.openembedded.org/g/openembedded-architecture/message/2313 Mute This Topic: https://lists.openembedded.org/mt/118543579/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-architecture/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
