I think you mean 3 releases. we have 3 arches for epel5 and epel6 and 2On Tue, 12 Aug 2014 21:05:07 +0200
Stephen John Smoogen <firstname.lastname@example.org> wrote:
> Where are we now:
> We support 3 arches.
> RHEL4: 1258 srpms. EOL
> RHEL5: 3651 srpms
> RHEL6: 5449 srpms
> RHEL7: 3100 srpms and growing fastest
>something to consider is moving epel to /opt/fedora/epel or somewhere> * Maybe as the way to implement EPIC rather than EPEL.
> * Policy change that allows for regular major changes in EPEL.
> * Can't update at any times.
> * Can make incompatible changes on the next point release of
> * Example: When RHEL7.1 comes out we have a 30 day window to get
> packages updated and new packages in that make incompatible changes.
> * Archive 7.0. The toplevel 7 tree is a symlink to whatever point
> release is latest.
> * Formalize the governance of EPEL.
> * Written policies of some sort for decision making
> * Elections?
> * Problems to solve:
> * Don't want to just listen to the people who are loudest
> * Don't want to just listen to the people who have been around the
> * Do we want automated testing of EPEL? yes. get it working on
> whatever subset you can and we'll go on from there.
> * Move to CentOS as build system? Gives us additional arches.
> * Could we do an ISV program like quaid does?
like it, then dealing with overlap etc should be simpler, but it would
take a massive change in packaging and could really only be done in