With yoe distro we always follow trunk based developement where we make monthly release tags but always live on master. This has been going for almost 2 years and we have managed to make this work with some challanges to fix upstream yocto layers where we could have lived on a long term release branch or something but its time worth spent. It was nice to know that there are other projects who also have same philosophy
We’ve spoken publicly about Google’s internal code base, and our efforts to keep that code maintainable as it grows. With over 250M lines of C++ code and nearly every project building from head, we’ve demonstrated a different approach to software engineering: one largely free of version mismatch issues and one where even the most common libraries can be refactored regularly, and safely. With Abseil we aim to bring some of that experience to the Open Source world.
We believe that the current paradigm for software is inherently unsustainable: dependency management is brutally complex. Unsolvable “diamond dependency” issues are common — the only ways to avoid these are to never change, or to ensure that there aren’t multiple versions. We prefer the latter, so we will do what we can to get you to live at head along with us — if everything is built from source at head, there can be no more diamond dependencies, branch conflicts, and complicated discussions about merge policy. All of that time spent could be spent on more useful things, like actually writing code and solving problems for users. Join with Abseil, and stop paying the content-management tax!
Good stuff!
Arch Linux is another good example of this philosophy – it works very well!
thats right, gentoo is also in there somewhere. but I think arch is just amazing.
so we had a regression in meta-freescale and yoe distro nightly builds noticed it first see
There are benefits of living on trunk ( rolling release model ), I wish this becomes a new buzzword in Opensource in 2024 
This is live information from Yocto project AutoBuilder on unpatched CVEs in various release branches of meta-openembedded layers. As can be seen, master branch is tending downwards but the time released branches are tending upward and older they are more unpatched CVEs they have. If you are a small firm, staying on master is a viable way to move in this world where every devices is connected and prone to be hacked.
https://autobuilder.yocto.io/pub/non-release/patchmetrics-meta-oe/
1 Like