Where to find proper bugs

[Matt Fischer]

On 04/10/2013 07:19 PM, Robert Bruce Park wrote:
> On Wed, Apr 10, 2013 at 05:38:14PM -0500, Javier P.L. wrote:
>> Whenever I want do triaging I look at these lists:
>>
>> http://tinyurl.com/5uxg9a Bugs with no package assigned
>> http://tinyurl.com/ydwayom New bugs
>> http://tinyurl.com/c7wok2e New security bugs
> Those are really good links, thanks! I have just bookmarked them.
>
> Here's another really good one to keep an eye on:
>
> http://tinyurl.com/bqqgc9b
>
> That link shows NEW *or* CONFIRMED bugs (remember, 'confirmed' just
> means that more than one person is affected; it still needs triaging),
> sorted by oldest first, because it's kind of embarrassing how old some
> of these untriaged bugs are...
>
> Come on, guys! Only 97,706 untriaged bugs left to go! We can do it! ;-)
>
Sometimes I find that the new/no-package bugs are not so easy to isolate 
to a package, so when I really want to make progress and try to get that 
number down below 97700, I take a slightly different approach. Maybe you 
can consider this option too: I pick packages that I am familiar with, 
use a lot, or have an interest in. I try to clean up the new bug list 
first, confirming, duping, and triaging if possible. After a few passes 
through the list you can usually make a dent in dupes and unconfirmed 
bugs. I'll then spend some time on older bugs, seeing if they've been 
fixed upstream or need more info.

Good luck!


-- 

Matthew (Matt) Fischer
LP: http://launchpad.net/~mfisch
IRC: mfisch