We had a discussion about this issue in our releng meeting on Jul 10th 2017. The problem is that there is no good way of solving this issue, but we came up two options:
1. Blocking the pkgs at branching and unblock them as necessary, pkg maintainers will request to unblock them and releng will review them and unblock them. Advantage is that we will more aware of whats got blocked and whats got unblocked. But it needs releng handling the tickets and we are not sure how many will show up per release cycle.
2. Using bodhi with greenwave to block pkgs. And config waiverdb to waive certain pkgs even if they are having dep issues so that they wont be blocked. And other pkgs can be blocked which can be unblocked by either releng or the pkg maintainer. We can configure it how ever we want like allowing only releng to unblock them when pkg maintainer files a ticket.
Please let us know what you think and we are open to any other suggestions.
_______________________________________________ devel-announce mailing list -- devel-announce@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-announce-leave@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
