-----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 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQGcBAEBCAAGBQJVJujOAAoJEAq0kGAWDrqleDoL/ikQf3oCjiMzghPrOBMx2TFt 6X02/f7e+nMIwSzitk2XSrikNuUYFsJel5ArSGfa5iwb2IjK2rxa+2WgSLTq0g/U GfBi839IffCD02MlmHMVg4Cu5bXuCCKYnkkIgt5PqcGABuANFZYvEdJCwFV+zY4D o4ZZe8dGbfGEHwsALGm/aSEtKThQOTz75NiLT3tReMggvBlEUbQTjWAsRJUbKCTN ZjTcZiGTHrkW1WIVfaTUlHNS7kcEJaFHSMuHEFN5s/BMA7W05h1r+gfOcOjZSYcg aDwwF54O5cZa7qMrFgFx/e5NQ7Ea5WaBc5v3liZge4HofY8oy63ZvznRudlZTdiM gIrK5Rcen9rV79Ykk5IdTUpHOCw54frhL43MR/bYJLlKj1d4es4EVepyN9nRjPot 9GFkGe8dfTZ/wdviXsX3Ia/yUVjuZ6303mAUNkeHTB/+/6HSPpJZL/655TMxiTmr vN98hKDw19TzPuaa1rcxoLb0iWrd+OLyGswTsuPpkA== =/eXz -----END PGP SIGNATURE-----