Actually, we need the automated resolution of old UNCO bugs to finally happen. A big percentage of UNCOs are either fixed on trunk or useless, there's no point in spending people's time on manual triage of those.

I agree that it would be nice if this could happen, but I'm not sure that we could schedule something like this with all the different agendas present in the Mozilla development community.

However, just outside the radius of the development community lies a fairly large pool of potential testers in the form of casual users. The paid Mozilla QA team is small and very busy — we just lost Sarah Liberman, a full-time tester, in June — but we are trying to get some initiatives off the ground to leverage this large, varyingly-skilled tester base.

So, for those (developer, casual user, whatever) interested in helping out with Mozilla QA, please check out the Mozilla Quality blog. Right now, the Mozilla QA team uses the blog as a clearinghouse for announcements and community testing help requests. For example, 1.5 is approaching quickly, and there will definitely be some testing help required there.

If we can generate some testing momentum in the general community, and can get some tools in place to make this interaction easier, the QA team can resume doing things like bug triage that have been traditionally quite helpful for developers, but have fallen off the map due to the regular testing burden.