From 35d89db8c2521e4717bf1dab691a661a3dc0d947 Mon Sep 17 00:00:00 2001
From: Orion Poplawski <orion@nwra.com>
Date: Oct 25 2024 13:58:33 +0000
Subject: Update modules/ROOT/pages/Package_Maintenance_Guide.adoc


Drop references to stream branches and package.cfg
---

diff --git a/modules/ROOT/pages/Package_Maintenance_Guide.adoc b/modules/ROOT/pages/Package_Maintenance_Guide.adoc
index 8a944ec..fd64ad9 100644
--- a/modules/ROOT/pages/Package_Maintenance_Guide.adoc
+++ b/modules/ROOT/pages/Package_Maintenance_Guide.adoc
@@ -222,35 +222,6 @@ and run a test build on it.
 fedpkg build
 ....
 
-=== Submit 'official' builds from a stream branch
-....
-fedpkg build
-....
-
-There is no difference in the command line
-to submit multiple builds from a stream branch.
-But you need to create a config file `package.cfg` in the repository
-and set option for the builds.
-For example config file is created in a stream branch `8` of package `foo`, which has content:
-
-[subs="attributes+"]
-....
-[koji]
-targets = f{MAJOROSVER} epel{MAJOREPELVER}
-....
-
-This example shows when you execute the `build` command,
-`fedpkg` is able to submit builds for releases, `f{MAJOROSVER}` and
-`epel{MAJOREPELVER}`.
-
-In practice, you are able to specify two shortcut names `fedora` and `epel` for convenience.
-`fedpkg` retrieves current active Fedora and EPEL releases automatically.
-Hence, if you do not want to select a subset of releases,
-or just simply going to build packages for active releases
-without knowing the concrete release name,
-shortcut names would be helpful.
-You can specify to build for `rawhide`, use name `master`.
-
 === Do a Container Layered Image Build
 ....
 fedpkg container-build