Post-mortem: Preventing broken updates from being pushed out?

Dear all, Following up on a broken update that got pushed: https://bodhi.fedoraproject.org/updates/FEDORA-2021-d42d8643e4 (I'm not naming the package here, as my goal with this discussion is not to assign blame but to figure out if we can prevent similar issues from reoccuring) Event timeline: - an update is created - one person upvoted it - someone noticed it is incomplete (because it relies on a separate update but was not pushed together -- previous iterations of the same update, done by a different user, normally bundle these two together). They left a comment but no negative karma - two more upvotes so the update got automatically pushed out - someone else finally provided negative karma but the package is already out IIRC we are making progress towards making sure updates are installable , and block pushes to stable based on that - is that coming soon? Also, this is the wiki page that describes how to provide feedback to updates: https://fedoraproject.org/wiki/QA:Update_feedback_guidelines (it's linked from https://fedoraproject.org/wiki/QA:Updates_Testing) It does not seem to have been changed much recently (I fixed a typo, but the previous update is from 2016). Should this be linked to from the Bodhi page and/or fedora-easy-karma, or a succint summary be shown on the web UI and the CLI tool? After browsing the page, it seems that it is slightly biased in favor of upvoting and/or leaving neutral feedback -- perhaps the use cases for providing negative feedback could be made more prominent (e.g. "negative karma will disable automatic push. If you think the update might break, do not hesitate to use this - you can always change your feedback later if you were mistaken".) Best regards, -- Michel Alexandre Salim profile: https://keyoxide.org/michel@michel-slm.name