On Wednesday, 03 February 2021 at 14:29, Kevin Kofler via devel wrote: > Jonathan Wakely wrote: > > Instead of force pushing or reverting anything in the rawhide branch, > > why not just have two branches? > > > > Maintainers commit to one branch, and if the build is successful that > > branch is automatically merged (as a fast-forward merge) to a > > "rawhide-build" branch. > > > > That way you know that what's on the rawhide-build branch was able to > > successfully build (at one time ... it might fail later due to changes > > to other packages). > > > > That avoids any automated (and possibly error prone) resets or reverts > > on the branch that the maintainer pushed to. > > But it means that provenpackagers who want to bump and rebuild have to > actually manually look at another branch (rawhide-build). No, why would they need to do that? The question aside, they wouldn't be allowed to do that, anyway. The idea is that only CI can push there once there's a successful build from rawhide branch. > Plus, they will then need to revert rawhide to rawhide-build, Again, why? Regards, Dominik -- Fedora https://getfedora.org | RPM Fusion http://rpmfusion.org There should be a science of discontent. People need hard times and oppression to develop psychic muscles. -- from "Collected Sayings of Muad'Dib" by the Princess Irulan _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
