On Thu, Apr 29, 2021 at 06:05:30PM -0400, Randy MacLeod wrote:
To be honest I don't see much value of these tags for layers notHi Armin,That could open up a can of worms as who will fix the QA test failures?Most yocto layers have not adopted the tagging perhaps because theyI think this could be a good thing, although it does put the burden on
included in the QA testing with oe-core release.
I believe we agreed on promoting latest revisions in the branches for
And I think the process for stable branches works reasonably well in the
layers I usually use and only very rarely new regression is introduced
in stable branch so from my experience the latest revision is always better
than GA tag (or any tag for various point releases).
Why should anyone use yocto-3.3 tag of meta-oe if the harknott branch
has few more fixes and tip of hardknott branch was tested exactly the
same as the yocto-3.3 tag?
TLDR: Why should some low traffic layer have these tags which might point to
exactly the same commit for multiple release (when all of them
still parse, build and work correctly). Many layers don't feel the need
to create a separate branch for each release when the same master works
fine for last 3 Yocto releases. And I feel the pain when e.g. with
meta-ros the last 4 branches (dunfell, gatesgarth, hardknott, master)
are 99% identical, so whatever ROS update I merge to one of them gets
distributed across all of them and only rarely with some small
modification added only in some of them. Adding a yocto-3.3 tag there
won't make that commit any better than a tip of hardknott and it might
be actually a lot worse than tip of hardknott.