On Wed, Apr 2, 2014 at 3:55 PM, Mike Gilbert <flop...@gentoo.org> wrote: > On the packages I maintain, I tend to use the latest unstable version > of the software. Stabilizing them rarely crosses my mind. > > I rather like the semi-automated reminders. They come in handy for my > own packages, as well as the large, uncoordinated mess of libraries > that the python team is tasked with maintaining. >
++ I see no harm in people filing STABLEREQs when software has been around for a while. If it is inappropriate to stabilize a package without further coordination, just close the bug INVALID or such with a brief explanation. If a non-dev contributor wants to do the necessary coordination to file a better bug more power to them, and if not it is up to the maintainer. The bugs should be going to the maintainer first, and they should be responding one way or another in any case. If Arch teams are getting bugged with invalid STABLEREQs I'd say the problem is that the package should be maintainer-wanted. Another option might be to have a tag in metadata.xml that flags packages as never-stable or indicating that stabilization requires coordination, which might help with triage or getting bug filters to check first. Rich
