sorting bugs

[Walter Lapchynski]

One thing I've struggled with in trying to get new bug triagers on
board is helping them find which bugs to work on. I tend to follow the
Pareto rule: work on the 80% you can get to right away since the other
20% are likely to take 80% of your time.

So there are several strategies I have considered:
 * focus on invalidating or moving along New bugs
 * focus on moving Confirmed bugs upstream (but many involve EOL releases)
 * focus on high heat bugs
 * look through newest bugs
 * focus on bugs Lubuntu Packages Team is notified about
But I still haven't found one that's really good. Any suggestions?

Going forward, I think I'm going to work at trying to tag all bugs
dealing with LXDE (and eventually LXQt) "lubuntu" since a lot of the
bugs we get notified about are not so much about our core system, if
you will. For example, if Abiword isn't behaving (it's often not),
that's not as critical as lxsession misbehaving. I'd consider iBus to
be something not specific to LXDE, but essential to our core system,
so I'd include that. Does that seem like it makes sense? Is there some
way to use the Launchpad API to automate this?

And then there's developers. How do I help them sort through one bug
from another? I've found the priorities we have to be extremely broad.
I was considering the notion of a tag like "lubuntu-critical" or
something of the sort to help them get a little more granularity
within the different priorities. Does that make sense or is there
something else someone would suggest?
-- 
@wxl
Lubuntu Release Manager, Head of QA
Ubuntu PPC Point of Contact
Ubuntu Oregon LoCo Team Leader