On 28/01/16 10:10, Neal Gompa wrote:
I personally think you should. EPEL isn't supposed to
unreasonably
hold back when even the upstream project no longer maintains that
version. As long as all consumers of the nginx package are
appropriately updated (if necessary) and the transition notes are
documented, I don't see why not. However, the problem really comes in
with how to do get people to read the upgrade notes, as that's pretty
much the only way to make that work.
There isn't any way to ensure users read upgrade notes, except between
new versions of Fedora/RHEL (as major changes would be expected). This
will inevitably bite someone when their Nginx configuration isn't valid
after the update, which could for example be via yum-cron.
Kind regards,
Jamie