Doc issue in file Releng SOPs related to Bodhi #329

New issue

Open

opened 2024-11-06 17:47:16 +00:00 by mattia · 0 comments

mattia commented

2024-11-06 17:47:16 +00:00

Contributor

I think there are several issues with Releng SOPs regarding Bodhi command to create releases.

In https://docs.fedoraproject.org/en-US/infra/release_guide/sop_mass_branching/#_creating_rawhide_release the command reports --branch f42, but the release marked as Rawhide should have --branch rawhide.
I did post a PR in the past, but probably something has been lost moving content through sections.
However I'm not sure how to read the section: the title says "mass branching", so I suppose it means a new Rawhide release is created and the "old" rawhide which become branched should have the branch corrected to its true value (--branch f41 in this case).

Also, the warning box at https://docs.fedoraproject.org/en-US/infra/release_guide/sop_bodhi_activation/#_update_bodhi_rpm_release about the need to restart bodhi services should not be needed anymore, because recent Bodhi releases invalidates the cache when a releases create or releases edit command is issued.

I think there are several issues with Releng SOPs regarding Bodhi command to create releases. In https://docs.fedoraproject.org/en-US/infra/release_guide/sop_mass_branching/#_creating_rawhide_release the command reports `--branch f42`, but the release marked as Rawhide should have `--branch rawhide`. I did post a [PR](https://pagure.io/infra-docs-fpo/pull-request/14) in the past, but probably something has been lost moving content through sections. However I'm not sure how to read the section: the title says "mass branching", so I suppose it means a new Rawhide release is created and the "old" rawhide which become branched should have the branch corrected to its true value (`--branch f41` in this case). Also, the warning box at https://docs.fedoraproject.org/en-US/infra/release_guide/sop_bodhi_activation/#_update_bodhi_rpm_release about the need to restart bodhi services should not be needed anymore, because recent Bodhi releases invalidates the cache when a `releases create` or `releases edit` command is issued.