Hello, as Fabio has pointed out, you can use Packit to get your releases to Fedora via pull-requests. Packit supports both push and newly also pull workflow. (So you don't need to have access to the upstream repository because it gets the info about the new version from Release Monitoring.) Thanks to it being pull-request-based, there is a Fedora CI involved and you, as a maintainer, can see the build/test results and decide if this should go to Fedora or not. Plus, an automatic Koji build and Bodhi update is possible as well. It's easy to set up. Here is the documentation for the Fedora automation: https://packit.dev/docs/fedora-releases-guide#pull-from-upstream-job And don't be afraid to ask. We, as a Packit team, are happy to help. František Packit Product Owner..;) #packit:fedora.im (Element / Matrix) #packit:libera.chat (IRC) hello@xxxxxxxxxx @packit@xxxxxxxxxxxxx (Mastodon) On Mon, Aug 28, 2023 at 3:01 PM Sérgio Basto <sergio@xxxxxxxxxx> wrote: > > On Mon, 2023-08-28 at 13:52 +0100, Sérgio Basto wrote: > > On Mon, 2023-08-28 at 03:28 +0000, Ryan Bach via devel wrote: > > > Faster updates are always as plus. > > > > > > Should this be under infrastructure list? > > > > > > Thoughts? > > > > > > > if you got a scratch build completed in a bugzilla for example : > > > > https://bugzilla.redhat.com/show_bug.cgi?id=2231971 > > > > you may use my helper script update_from_bugzilla.sh > > > > `fedpkg clone package-foo; cd package-foo ; > > ../update_from_bugzilla.sh` > > forgot to add bugzilla number, so should be > > `fedpkg clone package-foo; cd package-foo ; ../update_from_bugzilla.sh > 2231971` > > > > > > Thanks in advance for all the work done to make this distro great. > > > _______________________________________________ > > > 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 > > > Do not reply to spam, report it: > > > https://pagure.io/fedora-infrastructure/new_issue > > > > -- > > Sérgio M. B. > > _______________________________________________ > > 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 > > Do not reply to spam, report it: > > https://pagure.io/fedora-infrastructure/new_issue > > -- > Sérgio M. B. > _______________________________________________ > 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 > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue _______________________________________________ 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue