On 19 Apr 2017 5:13 pm, "Stephen John Smoogen" <smooge@xxxxxxxxx> wrote:
It is goal setting time inside of Red Hat, so I have been having to
come up with a list of things I would like to get done by the end of
this "fiscal year" (ie Feb 28th 2018).
I thought this might be a good time for each EPEL Steering Committee
member to come up with a list of things and also for people to offer
what they would like seen done. Currently I have the following on my
list:
1. Clean up and consolidate the various wiki docs into pagure similar
to how Fedora Release Engineering has all of their documents
https://pagure.io/docs/releng/
2. Look at adding to our release structure to be similar to how IUS
does their builds. https://ius.io/ with old packages moved off to an
archives channel.
3. Branching out to CentOS build system for alternate builds
There's been a couple of attempts at getting SCL into fedora guidelines which haven't gone anywhere (last I read IIRC was that what might be considered valid for RHEL as a corporate entity is not necessarily valid for Fedora so no SCL as FPC don't agree with it).
This actively hurt EL6 as some projects, for example owncloud, had to be dropped and others, such as nextcloud or letsencrypt/certbot, could never be introduced.
The EOL date for EL7 is still a long way off but anything relying on PHP, for example, will soon need to be removed from EPEL7 as projects drop support for the long EOL'd php5.4
I'd really like to see an effort within EPSCO to address this. As Red Hat relies more on SCL for recent versions of certain applications there's less chance of a rebase of these which will affect what we can actually package in EPEL.
This could potentially tie into your point 3 as CentOS already had the SCL SIG that builds on the Red Hat SCL packages as an upstream.
_______________________________________________ epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
