On Tue, 2022-01-11 at 09:51 -0800, Troy Dawson wrote: > Last year I sent out an email asking if anyone was using EPEL Playground. > Nobody said they were. > I did an analysis of what was being built on epel8-playground. The only > builds being built were also being built at the same time on epel8. Thus, > it appeared that nobody that was building on it was using it for it's > intended purpose. > An EPEL issue was opened, and a discussion was had in the EPEL Steering > Committee. All agreed that it was time to turn off EPEL Playground.[1] > > It is time to shut it down. I believe these are the steps. > > * Update Documentation [2] (pull request) > * Remove from mock configs [3] (merged, currently in testing) > * Remove configs from epel-release (todo) > * Archive repo (todo) > * Officially announce that EPEL Playground has gone away (todo) > * Steps I didn't think of (possible) What about removing all the package.cfg files in epel8 branches which is causing epel8 builds to simultaneously be built in epel8-playground? -- Yaakov Selkowitz Senior Software Engineer - Platform Enablement Red Hat, Inc. _______________________________________________ epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
