From Fedora Project Wiki
(more edits) |
(more edits) |
||
| Line 22: | Line 22: | ||
* Updates? | * Updates? | ||
* How do new packages enter the collection/branch? Fedora maintainer? Reviews? | |||
== Policy questions == | == Policy questions == | ||
| Line 31: | Line 33: | ||
* Would packages in this be able to conflict with epel packages? Base packages? | * Would packages in this be able to conflict with epel packages? Base packages? | ||
* When would incompatible changes be allowed? | * When would incompatible changes be allowed in each branch? | ||
Revision as of 16:56, 22 August 2014
EPEL faster repo ideas
This is a container wiki page for ideas around a sperate repo from EPEL that has different policies and expectations. Note that this is all just ideas and not set in any way at this time.
Three repos?
We could have 3 repos for the various needs:
- epel - stays the same as it is now.
- epel-rolling - allows some incompatible upgrades via some process, no overlaps, might have different life cycle
- epel-edge - allows overlapping with base and incompatable via some process, might have different life cycle.
Technical questions
- Would this repo use fedora infrastructure alongside epel? Or CentOS infra?
- Seperate branches?
- What does it build against?
- Updates?
- How do new packages enter the collection/branch? Fedora maintainer? Reviews?
Policy questions
- How many repos? epel, epel-rolling and epel-edge?
- What would faster moving mean?
- Would packages in this be able to conflict with epel packages? Base packages?
- When would incompatible changes be allowed in each branch?