#10555 Decommission epel8-playground in koji and bodhi
Closed: Fixed by humaton. Opened by tdawson.

  • Describe the issue
    EPEL Playground never really worked out and ended up being more burden than helpful. The EPEL Steering Committee has approved decommissioning epel8-playground.

I am not sure of all the steps.
At the very least, the epel8-playground and epel8-playground-candidate build targets need to be disabled in koji.
If possible, all the epel8-playground related tags and targets removed. And repo's cleaned out, and removed.
For bodhi, I don't know what needs to be done to decommission epel8-playground. It shouldn't be tagging anything into epel8-playground -testing, or epel8-playground. Maybe the koji changes are all that's needed. Maybe not. I don't know.

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

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

  • If we cannot complete your request, what is the impact?
    Nothing dramatic will happen if this isn't done. But currently epel8-playground isn't being useful for anyone, and thus, the resources allocated to it are being waisted.


Metadata Update from @kevin:
- Issue tagged with: low-gain, medium-trouble, ops

Did in https://pagure.io/fedora-infra/ansible/pull-request/944

Tags and targets are removed, ansible changes merged. I will run the playbooks shortly.

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

Metadata