On Sat, 2026-03-28 at 15:18 +0000, Peter Kjellerstedt via lists.openembedded.org wrote: > > -----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.
I think we need to go with yocto-6.0 since I remember there were a lot of issues with 6.0.0 although I don't remember exactly what they were offhand. > > 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. We have too much legacy around in general and we're effectively drowning in it. If you already have checkouts the tags will remain, this will just remove them from the repos and give people a good hint which ones to use going forward. Only duplicate and hence confusing tags will be removed where a given commit is referenced by multiple tags. I think we want clear repos rather than trying to keep archaeology at this point. If we did switch from master to main, we would need to remove the older one otherwise people would get confused. Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#2314): https://lists.openembedded.org/g/openembedded-architecture/message/2314 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]] -=-=-=-=-=-=-=-=-=-=-=-
