| |
@@ -8,26 +8,9 @@
|
| |
package collection. For general EPEL package guidelines, refer to the
|
| |
xref:epel-policy.adoc[EPEL Guidelines and Policy] page.
|
| |
|
| |
- [[beta_releases]]
|
| |
- == Beta Releases
|
| |
-
|
| |
- When a new Enterprise Linux major version (example 7, 8, 9) is being
|
| |
- tested and has been released as a open Beta version, EPEL will create a
|
| |
- Beta EPEL collection version against that release. This branch will
|
| |
- follow a process much like Fedora's rawhide repository. Packages built
|
| |
- in this Beta EPEL will be signed and pushed out each day. There will be
|
| |
- only one repository (no testing). Packages in this Beta collection could
|
| |
- be removed, or updated in an incompatible manner if needed before the
|
| |
- collection is released as stable. At some point after the Enterprise
|
| |
- Linux version is released, EPEL will leave Beta status and move to a
|
| |
- stable model for this collection.
|
| |
-
|
| |
[[stable_releases]]
|
| |
== Stable Releases
|
| |
|
| |
- Once a Enterprise Linux is released, and EPEL has left Beta and entered
|
| |
- it's stable phase the follow applies:
|
| |
-
|
| |
* All updates MUST spend at least 1 week in the testing repository, or
|
| |
+3 karma from testers.
|
| |
|
| |
carlwgeorge
commented a year ago
Starting in EPEL 9, we launch EPEL before RHEL by building against CentOS Stream initially. We no longer have a beta release of EPEL. Remove the outdated policy to avoid confusion.