Hi all! > > > 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. >
I do second Peter here. There is a difference between cleaning up and breaking things for downstream users. This can cause existing older releases of downstream projects to fail to clone. Example1: someone uses repo and has the tag in the released manifest file Example2: someone uses kas with the tags in question * Don't do that. * You can add the new scheme for future tags and *in addition* add the new scheme to the old/deprecated tags to have consistency. But do not *delete* what is in the repo already - do not change history. Best regards, Jan-Simon
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#2315): https://lists.openembedded.org/g/openembedded-architecture/message/2315 Mute This Topic: https://lists.openembedded.org/mt/118579776/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-architecture/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
