EPEL branches

The epel10 branch is used to create builds for the leading EPEL 10 minor version repository. Prior to the CentOS Stream 10 end of life (which corresponds to the end of the RHEL 10 Full Support Phase), these builds are built against external repositories of the matching major version of CentOS Stream 10.

These builds will indicate the minor version they are targeting in their dist tag using the format of .el10_x, where x is the minor version. They are published in the pub/epel/10 dnf repository for consumption by CentOS Stream 10, which is a symbolic link to the latest pub/epel/10.x dnf repository.

After the CentOS Stream 10 end of life (which corresponds to the beginning of the RHEL 10 Maintenance Support Phase), these builds are built against external repositories of the final minor version of RHEL 10.

The epel10.x branches (where x is the minor version, e.g. epel10.0) are used to create builds for the trailing EPEL 10 minor version repositories. These builds are built against external repositories of the matching minor version of RHEL 10.

These builds will indicate the minor version they are targeting in their dist tag using the format of .el10_x, where x is the minor version. They are published in pub/epel/10.x dnf repositories for consumption by the corresponding RHEL 10 minor version.

Each epel10.x branch lifetime depends on its corresponding RHEL 10 minor development and release process.

Before CentOS 10 starts receiving changes corresponding to a new RHEL minor release, a new epel10.x+1 branch is created by cloning the packages of the current active epel10.x branch. During this period, new builds against the epel10 branch will start landing in the new epel10.x+1 tag to become candidates for the new epel10.x+1 Bodhi release. New updates on the epel10.x branch are built against a CentOS 10 snapshot until its corresponding RHEL 10 minor release is available.

When a RHEL10 minor version stops being the leading release, its corresponding epel10.x branch goes end-of-life. This means that new package builds won’t be accepted and its contents will be archived.

Exceptions to this are the first minor branch, which is made arround the CentOS 10 release, and the one associated to the last RHEL minor release, which follows the regular EPEL branch lifetime policies.

The epel9 branch is used to create builds for the EPEL 9 repository. These builds are built against external repositories of the matching major version of RHEL 9.

They are published in the pub/epel/9 dnf repository for consumption by both RHEL 9 and CentOS Stream 9. EPEL 9 has no connection to RHEL 9 minor versions, and is always built against the current RHEL 9 minor version.

The epel9-next branch is used to create builds for the EPEL 9 Next repository. These builds are built against external repositories of the matching major version of CentOS Stream 9.

They are published in the pub/epel/next/9 dnf repository for consumption by CentOS Stream 9.

epel9-next branches are optional, and maintainers usually do not need to create them. You can read more about EPEL 9 Next and when it is needed here.

The epel8 branch is used to create builds for the EPEL 8 repository. These builds are built against external repositories of the matching major version of RHEL 8.

They are published in the pub/epel/8 dnf repository for consumption by RHEL 8. EPEL 8 has no connection to RHEL 8 minor versions, and is always built against the current RHEL 8 minor version.