Remove epel8-playground repo

Update playground section in README-epel-8-packaging.md

Signed-off-by: Troy Dawson <tdawson@redhat.com>

README-epel-8-packaging.md

@@ -52,50 +52,15 @@ other EPEL or Fedora branches.
 
 ## EPEL Playground
 
-We have added an additional set of channels for EPEL-8 called
+EPEL Playground was shut down in January 2022
-playground. It is meant to be sort of like Fedora Rawhide so that
+
-packagers can work on versions of software which are too fast moving
+EPEL 8 Playground was a place that developers and maintainers could 
-or will have large API changes from what they are putting in the
+"play around" with updated, or changed packages in epel. EPEL Playground
-regular channel.
+never really worked out and ended up being more burden than helpful.
-
+
-To try and make this transparent, we have made it so when a package is
+If developers or maintainers want something similar to EPEL Playground 
-built in epel8 it will normally also be built in
+we recommend Fedora COPR, which has availability for EPEL builds.
-epel8-playground. This is done via a packages.cfg file which lists the
+
-targets for fedpkg to build against. A successful package build will
-then go through 2 different paths:
-
-* epel8 package will go into bodhi to be put into epel8-testing
-* epel8-playground will bypass bodhi and go directly into
-  epel8-playground the next compose.
-
-If a packager needs to focus only on epel8 or epel8-playground they
-can edit packages.cfg to change the ```target= epel8
-epel8-playground``` to ```target= epel8 ```.
-
-Packages in epel8-playground are primarily to be used in the following
-manner:
-
-* To test out some new version of the package that might not be stable
-  yet.
-
-* To test out some new packaging of the package
-
-* To test a major version change of the package that they want to land
-  at the next epel8 minor release.
-
-* To build a package that will never be stable enough for epel8, but
-  still could be useful to some.
-
-* At minor RHEL releases (ie, 8.1, 8.2) people can pull in big changes
-  from playground to the main epel8 packages. Since people will be
-  upgrading and paying more attention than usual anyhow at those
-  points, it’s a great chance to do that change, but also you want to
-  make sure it’s panned out, so you can test before hand in
-  playground.
-
-Consumers should be aware that packages in EPEL8-playground are there
-without any Service Level Expectations. You may want to only cherry
-pick packages from there as needed.
 
 ## Developer request for branching multiple packages
 

epel-playground.repo

@@ -1,30 +0,0 @@
-[epel-playground]
-name=Extra Packages for Enterprise Linux $releasever - Playground - $basearch
-# It is much more secure to use the metalink, but if you wish to use a local mirror
-# place its address here.
-#baseurl=https://download.example/pub/epel/playground/$releasever/Everything/$basearch/os
-metalink=https://mirrors.fedoraproject.org/metalink?repo=playground-epel$releasever&arch=$basearch&infra=$infra&content=$contentdir
-enabled=0
-gpgcheck=1
-countme=1
-gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-8
-
-[epel-playground-debuginfo]
-name=Extra Packages for Enterprise Linux $releasever - Playground - $basearch - Debug
-# It is much more secure to use the metalink, but if you wish to use a local mirror
-# place its address here.
-#baseurl=https://download.example/pub/epel/playground/$releasever/Everything/$basearch/debug/tree
-metalink=https://mirrors.fedoraproject.org/metalink?repo=playground-debug-epel$releasever&arch=$basearch&infra=$infra&content=$contentdir
-enabled=0
-gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-8
-gpgcheck=1
-
-[epel-playground-source]
-name=Extra Packages for Enterprise Linux $releasever - Playground - $basearch - Source
-# It is much more secure to use the metalink, but if you wish to use a local mirror
-# place its address here.
-#baseurl=https://download.example/pub/epel/playground/$releasever/Everything/source/tree/
-metalink=https://mirrors.fedoraproject.org/metalink?repo=playground-source-epel$releasever&arch=$basearch&infra=$infra&content=$contentdir
-enabled=0
-gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-8
-gpgcheck=1

epel-release.spec

@@ -1,6 +1,6 @@
 Name:           epel-release
 Version:        8
-Release:        13%{dist}
+Release:        14%{dist}
 Summary:        Extra Packages for Enterprise Linux repository configuration
 
 License:        GPLv2
@@ -20,7 +20,6 @@ Source100:      epel.repo
 Source101:      epel-testing.repo
 Source102:      epel-next.repo
 Source103:      epel-next-testing.repo
-Source104:      epel-playground.repo
 Source105:      epel-modular.repo
 Source106:      epel-testing-modular.repo
 
@@ -59,7 +58,7 @@ install -Dpm 644 %{SOURCE0} \
 
 # yum
 install -dm 755 %{buildroot}%{_sysconfdir}/yum.repos.d
-install -pm 644 %{SOURCE100} %{SOURCE101} %{SOURCE102} %{SOURCE103} %{SOURCE104} %{SOURCE105} %{SOURCE106} \
+install -pm 644 %{SOURCE100} %{SOURCE101} %{SOURCE102} %{SOURCE103} %{SOURCE105} %{SOURCE106} \
     %{buildroot}%{_sysconfdir}/yum.repos.d
 install -pm 644 -D %{SOURCE3} %{buildroot}%{_prefix}/lib/systemd/system-preset/90-epel.preset
 
@@ -71,7 +70,6 @@ install -pm 644 -D %{SOURCE3} %{buildroot}%{_prefix}/lib/systemd/system-preset/9
 %config(noreplace) %{_sysconfdir}/yum.repos.d/epel-testing.repo
 %config(noreplace) %{_sysconfdir}/yum.repos.d/epel-modular.repo
 %config(noreplace) %{_sysconfdir}/yum.repos.d/epel-testing-modular.repo
-%config(noreplace) %{_sysconfdir}/yum.repos.d/epel-playground.repo
 %{_sysconfdir}/pki/rpm-gpg/*
 %{_prefix}/lib/systemd/system-preset/90-epel.preset
 
@@ -82,6 +80,10 @@ install -pm 644 -D %{SOURCE3} %{buildroot}%{_prefix}/lib/systemd/system-preset/9
 
 
 %changelog
+* Fri Jan 28 2022 Troy Dawson <tdawson@redhat.com> - 8-14
+- Remove epel8-playground repo
+- Update playground section in README-epel-8-packaging.md
+
 * Fri Sep 03 2021 Mohan Boddu <mboddu@bhujji.com> - 8-13
 - Change the baseurl to point to source/tree for srpms