Re: A general plea: please stop creating static, manually-updated lists of Fedora releases

Aaron Rainbolt <[email protected]>
Newsgroups gmane.linux.redhat.fedora.devel
Message-ID <CAFfBHfYshGFdx5a68G5qJjGXzsm-zHn1qVfU4cGi00tDBd6k5w@mail.gmail.com>
On Thu, Aug 20, 2026 at 1:43 PM Adam Williamson
<[email protected]> wrote:
>
> Once again, I'm on a round of "branching happened and all these things
> that have static lists of Fedora releases didn't notice".
>
> Exhibit A: https://gitlab.com/fedora/bootc/base-images/-/work_items/83
> Exhibit B: https://github.com/coreos/fedora-coreos-tracker/issues/2210
> Exhibit C: https://gitlab.com/fedora/bootc/base-images/-/blob/main/RELEASE.md#part-3-managing-fedora-versions-in-konflux
>
> yes these all happen to be bootc/coreos-related, but there are plenty
> of offenders, that's just where I'm looking today.
>
> The Fedora release cycle moves quite fast. Something important happens
> approximately every two months: a release branches, or goes stable, or
> goes EOL. You are not going to reliably keep up with this manually, and
> you should not be trying.
>
> There are two fairly solid ways you can check on what releases exist
> and what state they're in:
>
> 1. https://bodhi.fedoraproject.org/releases
> 2. https://fedorapeople.org/groups/qa/metadata/release.json

The fact that both of these services are gated behind Anubis is not
going to help automated tooling access them at all...

--
Aaron

> The former has more information but requires a bit more effort to work
> with. The latter is minimal but easy to work with (all you really need
> to know is that, if the 'branched' list is empty, rawhide maps to
> 'highest stable plus 1'; if branched is populated, rawhide maps to
> 'highest branched plus 1'). Both are ultimately manually updated, but
> the relevant releng SOPs now all have "update these things" in them, so
> they get updated reliably. Certainly more reliably than your manual
> list.
>
> It would be really, really great if, when folks are inventing new
> things like this, they would handle this smartly. Either do not *have*
> a "list of known releases" at all, or ensure there is a reliable,
> automated process that updates it.
> --
> Adam Williamson (he/him/his)
> Fedora QA
> Fedora Chat: @adamwill:fedora.im | Mastodon: @[email protected]
> https://www.happyassassin.net
>
>
>
> --
> _______________________________________________
> devel mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> 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/[email protected]
> Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
-- 
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.