-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 09.04.2015 19:21, Stephen John Smoogen wrote:
The problem usually are reported in direct emails or IRC. We also see the opposite emails where the developers are wondering why their package wasn't put in EL-6 or EL-7 when they had it in EL-5... but the release group decided it was better to surprise on the side of caution (eg no branch into EL-X)
I don't get why either side (user or developer/maintainer) needs to get "surprised"?
Couldn't a simple mechanism exists which asks every package maintainer before a new epel release gets created if his package should be included there (a mail with a link to website with a yes/no button would suffice, or something similar)?
you could also create opt-in or opt-out of such a function if people find it too annoying (after all it's just one email every X years).
this of course assumes you have mail addresses of maintainers at hand. I don't know if this is the case, but I hope so.
And of course someone would have to work out this stuff.
kind regards
Sven