Can podman get an exception to publish RC updates to stable Fedora testing repos?
As per the policy
Bodhi updates should only be created for builds which are expected to qualify for being pushed to stable. Maintainers should not use Bodhi’s testing states to test updates they never intend to push stable. This sort of testing should be done in Copr or other seperate public repositories. Consult with the QA team for further testing assistance.
We dont want to push RC's to stable but we want them get tested in Fedora since copr doesn't give us enough visibility and testing,
RE: https://bodhi.fedoraproject.org/updates/FEDORA-2025-bbe095a7d8
@lsm5 FYI.
Thank you.
It's a FESCo policy, you can't get an exception from us. But we can provide you with an opinion :-) I suggested having a discussion thread about this, because multiple teams could get involved easily. But in this ticket, we can give you at least Quality view. Let's discuss it in a meeting today.
Metadata Update from @kparal: - Custom field story_points adjusted to 2 - Issue priority set to: wishlist (was: normal) - Issue set to the milestone: Fedora 44 - Issue tagged with: meeting
We talked about this in our meeting yesterday: https://meetbot-raw.fedoraproject.org/teams/quality/quality.2025-11-10-16.00.log.html
We understand that this is beneficial for you, but we're not convinced that it is a correct path to take. We have test days that we can offer you, and you can also create COPRs and encourage interested users to have them installed long-term. You can also push the RC to Rawhide and see some users use it there. To be clear, we're not strongly against your idea, but also not too much in favor of it. Adam summarized it as "Meh!" :-D It makes the purpose of the updates-testing repo less clearly defined, for Quality and users, if there are suddenly packages that behave differently and their expectations are different.
If you want to continue this practice, it would be best to go directly to FESCo and either ask for an exception (there are already a number of exceptions listed in the policy), or present your case and ask FESCo to create a general rule for cases like yours (not just podman explicitly, but any package that wants to use this "test RC long-term" approach).
Metadata Update from @kparal: - Custom field story_points adjusted to 1 (was: 2)
Metadata Update from @kparal: - Issue assigned to kparal
I'll close this ticket as resolved, but feel free to respond or reopen it, if there's something else you want to see from us. Thanks.
Metadata Update from @kparal: - Issue close_status updated to: Wontfix - Issue marked as blocking: #2 - Issue status updated to: Closed (was: Open)
This issue has been migrated to Fedora Forge: https://forge.fedoraproject.org/quality/tickets/issues/841
Please continue any further discussion there.