Am 19.02.2016 um 16:53 schrieb Dave Johansen:
But as was also mentioned, a lot of packages have jumped on the
Chrome
bandwagon with crazy release cycles and maintaining security fixes in those
cases is basically impossible for a volunteer effort. From my perspective,
having a policy that "discourages but allows updates" with a very deliberate
and controlled process is the right model for EPEL.
Sounds good to me.
Also as a sysadmin I dislike that stuff in EPEL can change at any time
(whenever the maintainer can not support the old version anymore). If EPEL had
some kind of "release" (e.g. tied to RHEL point releases) I'd like to see
"most" incompatible upgrades happen at that time - with some kind of release
notes where I can read about the changes before.
Ideally I have some time (e.g. a month or so) to schedule the upgrade and deal
with any fall-out.
If that's possible with Stephen's rechartering I'm more than happy.
Felix