#12946 Document OpenH264 repo update process post-branching in releng SOP
Closed: Fixed by jnsamyak. Opened by jnsamyak.

  • Describe the issue
    As discussed during the Fedora 43 mass branching retrospective in the releng weekly meeting, we need to document the process for updating the OpenH264 repository after each branch.

Currently, after branching, the fedora-cisco-openh264-rawhide repo may still point to the previous release, causing mismatched GPG signatures on Rawhide. This was tracked in #12880

  • When do you need this? (YYYY/MM/DD)

ASAP, and before the next branching anyhow.

Action Items:

Add a section in the Mass Branching SOP (docs.fedoraproject.org/en-US/infra/release_guide/sop_mass_branching/) covering the OpenH264 update process.

  • When is this no longer needed or useful? (YYYY/MM/DD)

When Fedora stops OpenH264 work or releases itself :P

  • If we cannot complete your request, what is the impact?

We will be stuck figuring it out as always, like #12880 issue.

Please check https://www.fedorastatus.org/ for any known
outages before filing issues on an outage.


Metadata Update from @jnsamyak:
- Issue assigned to jnsamyak

Metadata Update from @jnsamyak:
- Issue tagged with: docs, high-gain, medium-trouble

Metadata Update from @jnsamyak:
- Issue tagged with: sprint-0

Metadata Update from @jnsamyak:
- Issue untagged with: high-gain
- Issue tagged with: medium-gain

Metadata Update from @jnsamyak:
- Custom field blocking adjusted to 12880
- Issue marked as blocking: #12880

Pr for review is here; https://pagure.io/infra-docs-fpo/pull-request/409

Metadata Update from @jnsamyak:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

Metadata