The EPEL incompatible upgrades policy includes a parenthetical comment on point 2 "need some way to short-circuit this for critical security updates - i.e. remote root". I propose that that if one EPEL Steering Committee member gives permission, the package maintainer may go ahead and submit the update to testing while discussion continues. In addition I propose that it be applicable for updates fixing high severity vulnerabilities in addition to critical.

I think this is important because upstream has to announce these updates publicly before they can be discussed, and it would be in the best interest of users who want to immediately apply a security update to have an easy place to get it, the epel-testing yum repository.