On Fri, Sep 6, 2024 at 4:11 PM Carl George <carl@xxxxxxxxxx> wrote: > > 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 > > Quick note for anyone watching this thread, please keep in mind that > some pieces of the infrastructure will continue to be in flux until > the official launch. For example, our plan was to turn on automatic > bodhi updates until the official launch. That worked for a little > while and builds were created and moved to stable, but then that > stopped working once we tried to enable a bodhi compose. We've > implemented a separate compose outside of bodhi, but we need to > temporarily disable new epel10 builds and revert it to finish > processing builds that are still in "pending->testing" and > "pending->stable" states. I'll post here again once the builds can > resume. > > -- > Carl George We were able to get all of the in-between builds processed, and have re-enabled the new compose method. We've also re-enabled the build targets, and verified that a new build got an automatic update that moved to stable automatically, just like rawhide. Builds that are marked stable should be available in the buildroot as soon as the regen-repo task finishes, and then composed nightly. This pipeline should stay the same until the official EPEL 10 launch in Q4. That's when we'll switch to the standard EPEL pipeline, with manually created updates, a default one week testing period, and bodhi composes. Packagers can resume building for epel10 at their leisure. Let us know if anything doesn't seem to be working as expected. -- 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
