It’s just about time for the official launch of EPEL 10. I’ve created a checklist of items we need to complete for this.
We’ll be turning off automatic bodhi updates soon as part of this checklist, hopefully this week. For maintainers, that means that when you create an EPEL 10 build you’ll need to create the bodhi update yourself, just like you would for EPEL 9 or EPEL 8. We’ll also go back to the default of seven days in the testing repo before updates move to stable. If you need to build closely related packages together, you still have side tags (preferred) and buildroot overrides at your disposal.
I also want to remind maintainers to check for bugs that have been reported against your EPEL 10 packages. We’ve identified several that were built and released but are not installable. Most of these have had fail-to-install bugs filed already, and I intend to file bugs for the rest of them. If you get one of these bugs, please give it your prompt attention so we can have the repo in a healthy state by the time of the launch announcement. If you don’t think you’ll be able to resolve the installation problem within the next 5-10 days, reply as such in the bug and I can untag the build to remove it from the repo. The branch won’t be retired, so as soon as you resolve the installation problem it can be added back to the repo with a new build.