Andreas Enge <[email protected]> writes: > Am Sat, Mar 14, 2026 at 03:53:49PM +0100 schrieb Sergio Pastor Pérez: >> To tackle the stability problem, specially on the user side, I was >> thinking that we could rely on the git tagging mechanism. My proposal is >> to introduce a bot that will tag stable commits. So when the CI crosses >> certain substitute availability (could be a subset of packages deemed >> important for desktops) the bot will tag the commit on master. > > Why not, but things could be even better: > Reach 100% of packages that build. > Only push commits that do not break any of them :) > > This would leave us with packages that break non-deterministically, > so it would be possible to get the green light from one of the build > farms and a failure on the other one.
I'm not sure we can maintain a close to 100% ratio. And with our current setup, is it possible to only push commits that do not break any packages? As far as I know, that requires the CI to do the building of all dependents, only after confirming that nothing breaks, the committer will be able to push it manually. The problem is on that "manual" part, commits need to be authenticated, which means that we cannot have a bot automatically making the commits. Best regards, Sergio
