Do we want to keep API/ABI stable over the corresponding RHEL release?
I think yes, but then we should really make sure that some libs don't
go to EPEL (for an example of a lib I maintain there is libdap which
changes API every 6 months or so).
Is there something similar for apps, for example that searching paths
command-line options, config files, file formats, are backward
If we impose such constraints, maybe there could be a discussion before
a package enters EPEL. Not a formal review because there should be no
packaging/usability issues, but a verification that the package is
stable enough and there are enough people/firms interested such that
if the maintainer stops maintaining a package that needs work it won't
be really unmaintained.