epel/docs
8
0
Fork 3
Code Pull requests 4 Projects Activity

Incorporated cwgeorge reviewed items

Browse source 
Signed-off-by: Diego Herrera <dherrera@redhat.com>
This commit is contained in:
Diego Herrera 2025-10-06 17:53:28 -03:00
commit 8d6bba05c5
2 changed files with 4 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

5
modules/ROOT/pages/branches.adoc
View file

@ -68,8 +68,9 @@ They are published in `pub/epel/10.x` dnf repositories for consumption by the co
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 leading epel10.x branch.
During this period, new builds against the epel10 branch will start landing on the new epel10.x+1 branch.
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.

2
modules/ROOT/pages/epel-policy.adoc
View file

@ -315,7 +315,7 @@ For EPEL releases with minor versions (e.g. EPEL 10) the process is similar.
When a new RHEL minor version is released, the branch associated to the previous
minor release goes end-of-life.
This means that it should go through the same retirement process.
as a regular EPEL release.
The final minor release will be active until the end of overall EPEL major release.
[[upgrade_path_policy]]
== Upgrade path policy