[FastTrack] Proposal: gate all stable release updates on rmdepcheck #3656

Closed
opened 2026-07-22 01:00:31 +00:00 by adamwill · 12 comments

I proposed this recently on devel@ and discourse. Feedback was overall pretty positive, but there was a general feeling that it'd be a good idea to run it by FESCo.

I don't want to put this through the Change process, as I feel it's too heavy and this is not tied to the release cycle. It's a very trivial change to make in technical terms - it'd just be adding a new policy to https://forge.fedoraproject.org/infra/ansible/src/branch/main/roles/openshift-apps/greenwave/templates/fedora.yaml.j2 like this:

--- !Policy
id: "kojibuild_bodhipush_rmdepcheck"
{{ product_versions(rawhide='false', branched='false', eln='false') }}
decision_contexts:
  - bodhi_update_push_testing
  - bodhi_update_push_testing_critpath
  - bodhi_update_push_stable
  - bodhi_update_push_stable_critpath
subject_type: koji_build
rules:
  - !PassingTestCaseRule {test_case_name: fedora-ci.koji-build.rmdepcheck.functional}

reverting it would be similarly easy: just remove the rule. I'm asking for FESCo approval to go ahead and try this and see how it goes; if it causes too many problems I'll revert it, or FESCo can request that it be reverted.

CC @lecris

I proposed this recently on [devel@](https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/6CGV34SXCNCDCX2K7AJTC3EFHU3K7TFR/#6CGV34SXCNCDCX2K7AJTC3EFHU3K7TFR) and [discourse](https://discussion.fedoraproject.org/t/proposal-gate-all-stable-release-updates-on-rmdepcheck/196033/3). Feedback was overall pretty positive, but there was a general feeling that it'd be a good idea to run it by FESCo. I don't want to put this through the Change process, as I feel it's too heavy and this is not tied to the release cycle. It's a very trivial change to make in technical terms - it'd just be adding a new policy to https://forge.fedoraproject.org/infra/ansible/src/branch/main/roles/openshift-apps/greenwave/templates/fedora.yaml.j2 like this: ``` --- !Policy id: "kojibuild_bodhipush_rmdepcheck" {{ product_versions(rawhide='false', branched='false', eln='false') }} decision_contexts: - bodhi_update_push_testing - bodhi_update_push_testing_critpath - bodhi_update_push_stable - bodhi_update_push_stable_critpath subject_type: koji_build rules: - !PassingTestCaseRule {test_case_name: fedora-ci.koji-build.rmdepcheck.functional} ``` reverting it would be similarly easy: just remove the rule. I'm asking for FESCo approval to go ahead and try this and see how it goes; if it causes too many problems I'll revert it, or FESCo can request that it be reverted. CC @lecris
Owner

+1, seems reasonable.

+1, seems reasonable.
Owner

+1 and I hope to eventually enable this for rawhide and branched as well

+1 and I hope to eventually enable this for rawhide and branched as well
Owner

+1

+1
Owner

+1!

+1!
Owner

I'll also nominate this for fast-track. I think some fesco members are on vacation and unlikely to vote, but we don't have to wait a whole week.

I'll also nominate this for fast-track. I think some fesco members are on vacation and unlikely to vote, but we don't have to wait a whole week.
zbyszek changed title from Proposal: gate all stable release updates on rmdepcheck to [FastTrack] Proposal: gate all stable release updates on rmdepcheck 2026-07-22 10:39:25 +00:00
Owner

+1

Also hoping to see it for rawhide + branched too soon-ish :)

+1 Also hoping to see it for rawhide + branched too soon-ish :)
Owner

+1

+1
Owner

+1 and I'd like to see this across the board, really.

+1 and I'd like to see this across the board, really.
Owner

+1, seconded @ngompa's remark.

+1, seconded @ngompa's remark.
Owner

APPROVED (+8, 0, -0)

APPROVED (+8, 0, -0)
Author
https://forge.fedoraproject.org/infra/ansible/pulls/3545
Owner
Announced in https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/GGQQSJ2NVYJIH4TJKOOPEBZ4TX4VQCLI/
Sign in to join this conversation.
No milestone
No project
No assignees
9 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
fesco/tickets#3656
No description provided.