Good Morning Everyone, Based on the outcome of this discussion, I started trying to draw how the process to update a package in rawhide would look like with rawhide being gated on tests. There are currently two proposals: - one that does not involve bodhi updates - one that does Both proposals have a different flow for single-package update and multi-packages update. Here is what I came up with. Without bodhi: - Single package update https://pingou.fedorapeople.org/gating_rawhide/GatingRawhide.png - Multi-packages update https://pingou.fedorapeople.org/gating_rawhide/GatingRawhide_MultiplePkgs.png With bodhi: - Single package update https://pingou.fedorapeople.org/gating_rawhide/GatingRawhide_bodhi.png - Multi-packages update https://pingou.fedorapeople.org/gating_rawhide/GatingRawhide_MultiplePkgs_bodhi.png Outside of this workflow things we know we want to have/keep working: - Keep chain-build working -> would one of the proposal facilitate that? - Have a way to run tests against an entire side-tag before merging it - Have a way to ask the tools to re-check greenwave's decision (so that false negative can be waived and the process continued) mizdebsk suggested on IRC two ideas which I think would be worth looking into a little bit down the road once we got the basis done: - new side-tag could be automatically generated from fedpkg build command - packagers could define a list of packages that should be rebuilt in the side-tag and when all of these packages have been successfully rebuilt, the request to merge the side-tag is automatically created This would allow to use chain-build and let the entire process be automated. What do you think? Pierre
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
