It appears that fedpkg queries bodhi for releases, but that is not going to work as we have this period from when we branch f28 off until next month or so before we enable bodhi for f28. ;(

So, it needs to query the pdc I suppose and we need to get our change in so we can have 'pending' releases in pdc (instead of just development or stable).

@mprahl Can you take a look, I think you merged fedrepo_req and fedpkg? Or shall we file on fedpkg about this?

@kevin the backstory behind this is that the PDC API (https://pdc.fedoraproject.org/rest_api/v1/product-versions/) isn't up to date, so I couldn't use that as a source of truth. Instead, I chose to use Bodhi without realizing that there would be this lag between mass-branching and when the branch becomes active in Bodhi.

@mohanboddu is going to look into updating and maintaining that PDC API, and then I can submit a patch for fedpkg to use it. I don't control the release of fedpkg, perhaps we can ask them to do a hotfix release.

I figured out that as a quick fix, you can just create the ticket at https://pagure.io/releng/fedora-scm-requests manually, copy the json from another closed ticket to see the format.

I figured out that as a quick fix, you can just create the ticket at https://pagure.io/releng/fedora-scm-requests manually, copy the json from another closed ticket to see the format.

We can also use fedrepo-req-branch for now, which works properly, and avoid human mistakes.

Part of this is addressed in releng#7342.

The fedpkg change is in fedpkg#188

Lets close this in favor of the fedpkg change. Hopefully there will be a new release with this soon...