Closed bugs; no release

On Mon, Oct 4, 2010 at 4:43 PM, Daniel O'Connor wrote:
So, I just slogged through 2003's unreleased packages; and we're upto 2004.
http://pear.php.net/qa/packages_closed_reports_no_release.php

If we can't get a QA release out in around 6-7 years, I think it's safe to
say we should rethink the process a bit.
I'm worn out after doing a mere 10 or so of the 200+ pending releases.

What can we automate?
Can someone check the 'you have bugs open cron' too?
What restrictions can we abolish?

What can we do to maintain the spirit of
http://pear.php.net/pepr/pepr-proposal-show.php?id=60 whilst tweaking it to
deal with 200+ dead or dying packages?

My thoughts:
*Hand out PEAR QA karma to lots more active developers* - aim to get the
size of the active QA group to around 10-20.
Cull QA karma from inactive users. 6/12 months with no qa-ish actions =
thanks for your time.
Build trunk packages automatically (I got this bit working); and put them in
an easy publishing queue ("approve this release" => uploads .tar.gz, pear
svntags from package.xml) - help wanted