On 2019-09-26, Pierre-Yves Chibon <pingou@xxxxxxxxxxxx> wrote: > ○ Every changes to dist-git is done via pull-requests Pull requests are great for proposing your changes to foreign packages. It does not make sense when maintaining the code. Either when doing a mass changes like rebuilding all Perl packages against a new perl or when pushing your own changes. It will become a bureaucracy that adds a delay and complexity and spams you mailbox. Who is going to merge all the requests? How do you automate it? We would need "koji watch-task" for merging the pull requests. I will repeat it: pull requests are great when you need a review. Otherwise it only consusmes resources. I'm strongly against this. > ○ Pull-requests are automatically tested Nice. But i think this already happens. > ○ Every commit to dist-git (ie: PR merged) is automatically built in koji How do you want to implement waiting on propagating build root overrides? > ○ Every build in koji results automatically in an update in bodhi How do I merge related updates into on if more packages must be tested and delivered as one unit? That very often happens with the overrides. I smell automated side-tags that has never been implemented. > ○ Every update in bodhi is automatically tested This is already a reality. > ○ If the tests pass, the update is automatically pushed to the repository > This also already happens. -- Petr _______________________________________________ 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
