On Sat, Sep 07, 2024 at 04:11:07PM GMT, Paul Howarth wrote: > On Fri, 6 Sep 2024 19:19:46 -0500 > Carl George <carl@xxxxxxxxxx> wrote: > > We were able to get all of the in-between builds processed, and have > > re-enabled the new compose method. We've also re-enabled the build > > targets, and verified that a new build got an automatic update that > > moved to stable automatically, just like rawhide. Builds that are > > marked stable should be available in the buildroot as soon as the > > regen-repo task finishes, and then composed nightly. This pipeline > > should stay the same until the official EPEL 10 launch in Q4. That's > > when we'll switch to the standard EPEL pipeline, with manually created > > updates, a default one week testing period, and bodhi composes. > > > > Packagers can resume building for epel10 at their leisure. Let us > > know if anything doesn't seem to be working as expected. > > Prior to this change, I was able to edit the automatic update and add a > bugzilla ticket reference to it so that the EPEL 10 branch request > ticket would be closed when the update was pushed to stable. > > Now, instead of having to add the bugzilla reference and push the > update to testing manually at the start of the update process, I need > to go and close the associated ticket manually at the end of the > process. It would be nice if this could be automated too. See https://bodhi.readthedocs.io/en/latest/user/fedora-flavored-markdown.html you can add rhbz#nnnnn to your changelog/git commit and bodhi will see it and associate that bug with that update. kevin
Attachment:
signature.asc
Description: PGP signature
-- _______________________________________________ epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-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/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
