We are nearing the ideal time to officially launch EPEL 10, roughly six months prior to the RHEL 10.0 release. Here are a list of items we need to complete for the launch.
I'll take "add epel-release to CentOS's extras-common repo" I'll wait a week, possibly two. But I'll let you know on this issue when it's done.
I'm going to take the "update new-updates-sync" and the "add instructions to getting started page"
https://pagure.io/fedora-infra/ansible/pull-request/2343 implements a good number of the items above. I'll cross them off once it's merged.
Metadata Update from @carlwgeorge: - Issue tagged with: meeting
epel-release has been built for CentOS Stream 10 extras-common repo. It has been tagged for release, but I don't know how long it takes for that repo to make it everywhere. https://cbs.centos.org/koji/buildinfo?buildID=56941
https://pagure.io/fedora-infra/ansible/pull-request/2365 should fix the symlink once it's merged.
Metadata Update from @carlwgeorge: - Issue marked as blocking: #305
Metadata Update from @carlwgeorge: - Issue unmarked as blocking: #305 - Issue marked as depending on: #305
PR 310 should tick off the "Getting Started" page box, and I think @carlgeorge's PR 309 ticks the "Add EPEL 10 Overview" box right?
Shall the What packages and versions are available in EPEL? section be updated as well?
@psss Thanks for catching that. I've pushed the fix in this commit. If you noticed anything else please do mention it, or even send a pull request to fix it directly.
https://communityblog.fedoraproject.org/epel-10-is-now-available/
Metadata Update from @carlwgeorge: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
This issue has been migrated to Fedora Forge: https://forge.fedoraproject.org/epel/steering/issues/300
Please continue any further discussion there.