From c9573f5621a72aba5de2ae4b91c0d90690ae4d3c Mon Sep 17 00:00:00 2001
From: Lenka Segura <lsegura@redhat.com>
Date: Jan 31 2025 10:55:05 +0000
Subject: [PATCH 1/2] sop_mass_branching: Remove PDC and update koji blocking section


Signed-off-by: Lenka Segura <lsegura@redhat.com>

---

diff --git a/modules/release_guide/pages/sop_mass_branching.adoc b/modules/release_guide/pages/sop_mass_branching.adoc
index 380bc95..18856e4 100644
--- a/modules/release_guide/pages/sop_mass_branching.adoc
+++ b/modules/release_guide/pages/sop_mass_branching.adoc
@@ -128,52 +128,10 @@ values.
 * https://src.fedoraproject.org/rpms/fedora-release
 * https://src.fedoraproject.org/rpms/fedora-repos
 
-== PDC
-
-The "product-release" needs to be created in PDC.
-
-In the `scripts/pdc/` directory, run:
-
-```
-$ python create-product-release.py fedora $TOKEN Fedora $NEW_VERSION
-```
-
-On `pdc-backend01.stg` (for testing) or `pdc-backend01` (for production)
-clone (or update an existing one) the releng repo:
-
-```
-$ git clone https://pagure.io/releng.git
-```
-
-In the `scripts/pdc/` directory, run (see the `--help` of the script for
-information on how to run it):
-
-```
-$ python create-new-release-branches.py ... --createfile
-```
-
-NOTE: The `--createfile` argument is necessary, that file is needed for the next step.
-
-[NOTE]
-====
-Due to memory leak issue in pdc, we need to set the config in
-`/etc/pdc.d/fedora.json`:
-```
-{
-  "fedora":
-    {
-      "host": "http://pdc-web02.iad2.fedoraproject.org/rest_api/v1/",
-      "develop": false,
-      "ssl-verify": false
-    }
-}
-```
-====
 
 == dist-git
 
-Now that pdc has the new release and each package has been branched in
-pdc we need to update dist-git in two steps:
+Now we need to update dist-git in two steps:
 
 * Create the new branch in git
 * Update the gitolite.conf to allow user to push to this new branch
@@ -182,7 +140,7 @@ For both of these actions you will need the file generated by pdc above.
 
 === Create the git branches
 
-On `pkgs01.stg` (for testing) or `pkgs02` (for production), run:
+On `pkgs01.stg` (for testing) or `pkgs01` (for production), run:
 
 ```
 $ sudo -u pagure python /usr/local/bin/mass-branching-git.py <new branch name> <input file>
@@ -603,15 +561,11 @@ $ rm -f latest
 $ ln -s ../f{rawhide}-build/latest ./latest
 ----
 
-=== Update block_retired.py script
-
-https://pagure.io/releng/blob/main/f/scripts/block_retired.py[block_retired.py]
-script in releng repo should be updated with rawhide release and also
-branched release should be added to the script.
-
-Please look at this
-https://pagure.io/releng/c/9eb97f491f7a767ab8b90498adfa3b34ee235247?branch=main[block_retired.py
-commit] as an example.
+=== Make sure branched release does not have set EOL
+Presence/absence of EOL date is the way the
+https://pagure.io/fedora-infra/toddlers/blob/main/f/toddlers/plugins/koji_block_retired.py[toddler
+koji_block_retired] distinguishes between stable and branched releases. EOL should be filled
+once a release becomes stable.
 
 === Updating MirrorManager
 

From eb0cf66c430f3443beeb77ee0f2242464b1226c8 Mon Sep 17 00:00:00 2001
From: Lenka Segura <lsegura@redhat.com>
Date: Jan 31 2025 10:55:05 +0000
Subject: [PATCH 2/2] mass_branching_checklist: Remove PDC


Signed-off-by: Lenka Segura <lsegura@redhat.com>

---

diff --git a/modules/release_guide/pages/mass_branching_checklist.adoc b/modules/release_guide/pages/mass_branching_checklist.adoc
index 59cc6b7..4b5f904 100644
--- a/modules/release_guide/pages/mass_branching_checklist.adoc
+++ b/modules/release_guide/pages/mass_branching_checklist.adoc
@@ -165,12 +165,6 @@ security_fixes = 'YYYY-MM-DD'
 * [ ] Configure an outage in Koji to disable Rawhide builds.
 * [ ] Cancel all running builds for Rawhide by listing and selecting relevant tasks, and then cancel each task.
 
-==== PDC (Product Definition Center)
-
-* [ ] Create a new "product-release" in PDC using the provided script.
-* [ ] Clone or update the releng repository on PDC backend.
-* [ ] Run the `create-new-release-branches.py` script to set up the new release branches, ensuring to use the `--createfile` argument.
-
 ==== Koji
 
 * [ ] Run the `make-koji-release-tags` script from the releng repository to handle builds from the new branch.