On 9/18/19 12:02 AM, Miroslav Suchý wrote: > Dne 17. 09. 19 v 18:28 Kevin Fenzi napsal(a): >> Branching is not just "oh, make a new compose". There's a ton of >> steps/work that happens then, including: >> >> * Making a new branch on all active rpms >> * Switching to a new signing key in rawhide. >> * New pungi-fedora config, new comps, new kickstarts. >> * Setting up new koji tags, etc. > > Is this process documented somewhere (Maitai, UML, jBPM)? I am only > aware of Fedora release schedule. > How many of these actions are triggered automatically and how many of > them has to be started by hand? Releng has scripts for it: https://pagure.io/releng/blob/master/f/scripts/branching and an SOP (although it needs some work): https://docs.pagure.org/releng/sop_mass_branching.html Most of the actions are human run. There's nothing really to trigger off of. If we had time we could possibly roll all of this into a ansible playbook or the like. kevin
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ 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
