I think this is all too big a hammer. There's lots of cases where people make small changes and don't think it's worth doing a new build, but expect it will get picked up in the next one. So, perhaps a more targeted approach might work? Say a week before the mass rebuild, add a comment to all 'stuck in gating' rawhide updates saying 'hey, the mass rebuild is starting in a week, please fix this or the day before the mass rebuild we will unpush this and revert git to the previous passing builds commit' Thats yet more work for releng/qe, but some/much of it might be automatable. kevin -- _______________________________________________ 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
