EPEL Renewed
summary
EPEL creates a separate EPEL8 path as a pub-alt repo and will not ship modules for the beta, building non-modular packages first with Fedora Koji and the modular field service doing later work. Packages target three channels: BaseOS AppStream CodeReady, and maintainers use stream branches so upstream can declare a lifecycle (e.g., two-year streams). Plans include a base-plus-updates/archive model so old point releases remain available, composed on a slower cadence and managed by volunteers rather than daily rawhide-style composes.
AI-written summary · about
chapters (13)
- 0:00EPEL introduction
- 2:56What EPEL is
- 8:51EPEL governance
- 11:00EPEL challenges
- 16:49EPEL 8 plans
- 22:28EPEL 8 channels
- 27:32EPEL 8 future
- 31:08Contributing to EPEL
- 39:19EPEL 8 modularity
- 42:50EPEL 8 timeline
- 47:32EPEL package popularity
- 49:29EPEL archiving
- 51:14Closing & Q&A
related talks
28mLinux distributions as an ultimate challenge of continuous integration and how we solve it.
34mFedora ELN at Meta: a testbed for fleet upgrades
46mCentOS Stream: What you need to know
25mCentOS Stream: Progress so far
35mBuilding the Community Enterprise Operating System through CentOS Stream
24mEveryone can contribute to RHEL now!
35mPackit: 2 years of upstream ⟷ downstream
48mIntegrating upstream projects downstream