On Thu, Oct 19, 2023 at 6:24 PM Adam Williamson <adamwill@xxxxxxxxxxxxxxxxx> wrote:
I'm not sure I have time to take this, but glancing over it, I have a
suggestion on how to further automate the release stuff.
You can use Bodhi release date to determine the extant EPEL releases
and the current Branched release. If you query
https://bodhi.fedoraproject.org/releases/ with content-type JSON, you
get a bunch of data on releases (paginated, so either handle the pages
or use https://bodhi.fedoraproject.org/releases/?rows_per_page=500
instead).
To get all current EPEL releases you'd do something like this:
epels = {int(rel['version']) for rel in releases if
rel['state'] == 'current' and rel['id_prefix'] == 'FEDORA-EPEL'}
To find current Branched, you can do something like this:
devrels = {int(rel['version']) for rel in releases if
rel['state'] == 'pending' and rel['id_prefix'] == 'FEDORA'}
if len(devrels) > 1:
branched = min(devrels)
else:
branched = None
that logic should be safe as long as we don't change the release
process. There is always one "pending" Fedora release - Rawhide. If
there's more than one, there will be two, and the other one will be
Branched.
Or, the "lazier" to implement alternative for this would be https://packager-dashboard.fedoraproject.org/api/v1/releases :)
Best regards / S pozdravem,
František Zatloukal
Senior Quality Engineer
Red Hat
_______________________________________________ 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
