From 88d1e20c522d79d24c60bf330d0659cc8e1e3ec3 Mon Sep 17 00:00:00 2001
From: Samyak Jain <samyak.jn11@gmail.com>
Date: Sep 11 2025 04:10:33 +0000
Subject: Add documentation regarding the openh264 work at the time of branching


Signed-off-by: Samyak Jain <samyak.jn11@gmail.com>

---

diff --git a/modules/release_guide/pages/sop_mass_branching.adoc b/modules/release_guide/pages/sop_mass_branching.adoc
index 2db829d..b2e80a2 100644
--- a/modules/release_guide/pages/sop_mass_branching.adoc
+++ b/modules/release_guide/pages/sop_mass_branching.adoc
@@ -55,6 +55,13 @@ This will iterate over all packages and sign them with the new f{rawhide_next} k
 Once complete, re-run the ./sigulsign_unsigned.py command to confirm all are signed.
 On branching day, remove the robosignatory config for this resigning.
 
+[NOTE]
+====
+The OpenH264 packages are **not included** in the general mass resigning
+process, since they live outside the main `f{rawhide}` tag.  
+These must be handled separately, please check with section below, and with the infrastructure folks.
+====
+
 == Send announcement
 
 One day before the mass branching, we send out announcemt because during mass branching,
@@ -674,6 +681,53 @@ this file, ask a member of the Quality team to do so.
 Once the branched compose is composed, we need to re-enable
 robosignatory on branched release.
 
+
+=== OpenH264 Repository Update After Branching
+
+At the day of Fedora branching and after the above process, the OpenH264 repository must be updated to ensure
+that Rawhide points to the correct release version.
+
+==== Problem
+When Fedora branches (e.g. from f{branched} to f{rawhide}), the `fedora-cisco-openh264-rawhide`
+repository may still reference the previous release. This causes mismatched GPG
+signatures because the `$releasever` used in the repository configuration
+expects the new Fedora key.
+
+==== Process
+
+. **Create a new repository for the branched release**
+  * A new `f{rawhide}` OpenH264 repository should be created in Koji.
+  * Ensure packages in this repository are signed with the Fedora {rawhide} GPG key.
+
+[source,bash,subs="attributes"]
+----
+$ koji dist-repo f{rawhide}-openh264 [SIGN_KEY_{rawhide}] --noinherit --with-src -a aarch64 -a x86_64 -a s390x -a ppc64le
+----
+
+. **Update MirrorManager**
+  * Update MirrorManager so that the `fedora-cisco-openh264-rawhide` entry now
+    points to the newly created `f{rawhide}` repository.
+  * Verify that the `$releasever` placeholder correctly resolves to `f{rawhide}`.
+
+[source,bash,subs="attributes"]
+----
+$ ssh os-control01.rdu3.fedoraproject.org
+$ oc rsh <pod_name> -- /bin/bash -n mirrormanager (pid_name should be the one starting with frontend*)
+Login using psql (db name is mirrormanager2), and then run the following update command fo redirection:
+$ UPDATE repository_redirect
+SET to_repo = regexp_replace(to_repo, '-{branched}$', '-{rawhide}')
+WHERE from_repo ILIKE '%openh264%';
+Once, this is done, update the fullfiletimelist as well, this sometime take time to reflect.
+----
+
+[%sidebar]
+====
+**Note:** A related issue was recently opened:
+- *Issue #12880* — missing Fedora 44 openh264 repo after branching.  
+  After F43 was branched, the openh264 Rawhide repo still points to F43's GPG key, causing signature errors. We now need an `f44` repo and to update MirrorManager accordingly. --See issue #12880 for details.
+  Remove once the process becomes normal or have a fix.
+====
+
 === ELN related work
 
 Add the new rawhide key to eln pungi config. For example, look at this
@@ -694,6 +748,7 @@ https://docs.fedoraproject.org/en-US/infra/sysadmin_guide/koschei/#_branching_a_
 Temporarily disable the rawhide cron job during branching PRs to ensure a branched compose is created. Re-enable rawhide after this.
 ====
 
+
 == Consider Before Running
 
-NOTE: FIXME: Need some love here
+Please check with community and infrastructure team, if there are blockers before branching.