On Thu, Jul 4, 2024 at 2:45 AM Carl George <carl@xxxxxxxxxx> wrote: > > I originally posted this on Fedora Discussion [0], but I'm sharing it > here as well for awareness. > > # Executive summary > > EPEL 10 is expected to be launched in Q4 of 2024. You may start > noticing parts of the infrastructure coming online sooner than that. > **Please do not start creating EPEL 10 builds until we announce that > we are ready for packagers to start building.** > > # Detailed description > > The EPEL Steering Committee has big plans for EPEL 10. These plans > are covered in detail in the original EPEL 10 proposal [1]. I also > presented an EPEL 10 overview at the Fedora 40 release party [2]. At > a high level, we are bringing minor versions to EPEL. I encourage you > to read the proposal or watch that video for a deeper explanation. > > I'm writing this post to share our planned timeline for EPEL 10, and > to set expectations for the coming months. Early CentOS Stream 10 > composes are already available [3], but it hasn't been officially > launched yet because the content set is still in flux. We expect to > see the official launch announcement for CentOS Stream 10 later this > year. We intend to align the EPEL 10 launch with that, which will > give us the following approximate timeline. > > - August 2024: EPEL 10 hackfest at Flock [4] (see below for more details) > - Q4 2024: expected launch of CentOS Stream 10 and EPEL 10 > - Q2 2025: expected launch of RHEL 10 (three years after RHEL 9) > > In the months ahead, you may notice parts of EPEL 10 infrastructure > coming online, such as build targets in Koji and releases in Bodhi. > We will need these infrastructure pieces in place to work out all of > the details of integrating minor versions. We'll send out an > announcement when EPEL 10 is ready for package maintainers to start > creating their builds. **Please do not start creating EPEL 10 builds > until we announce that we are ready for packagers to start building.** > Any builds created before this announcement may need to be discarded > and rebuilt. > > I will be running an EPEL 10 Hackfest at Flock [4] in August (next > month). The plan is to work on various infrastructure pieces related > to EPEL 10. If we happen to have most of these pieces working prior > to the hackfest, we can pivot our time to adding initial packages to > EPEL 10. I hope to see you there! > > [0] https://discussion.fedoraproject.org/t/epel-10-status-update/124549 > [1] https://discussion.fedoraproject.org/t/epel-10-proposal/44304 > [2] https://youtu.be/PxWxK5PgUuE > [3] https://lists.centos.org/hyperkitty/list/devel@xxxxxxxxxxxxxxxx/thread/QCO73CKFMPNMERUWIQ47OVJMMUM7YUXU/ > [4] https://flocktofedora.org/ > > -- > Carl George It's just about time for the official launch of EPEL 10. I've created a checklist of items [0] 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 [1] (preferred) and buildroot overrides [2] 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. [0] https://pagure.io/epel/issue/300 [1] https://docs.fedoraproject.org/en-US/package-maintainers/Package_Update_Guide/#_side_tags [2] https://docs.fedoraproject.org/en-US/package-maintainers/Package_Update_Guide/#buildroot_overrides -- Carl George -- _______________________________________________ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
