On 02/08/2012 12:07 AM, Bradley Woods wrote:
Hi everyone,
My group and I have selected to work on Shotwell for a project we are doing
in our Computer Science capstone. One of the things we are supposed to do
for an assignment is to triage bugs in the bug tracker. I was wondering if
there was any particular way in which that is done around here. If bug
triage isn't done by just anyone, that would be helpful to know as well.
Bradley,
I'm glad that you and your group are interested in helping out. I think
that triaging bugs means a few things. For each bug, we want to
1. Make sure that the bug description is clear and that the bug is
reproducible.
2. Make sure that the bug is actually something we want to fix or
implement. Sometimes this involves judgment, as some bug reports are
actually more like feature requests.
3. Choose an appropriate priority or target milestone for the bug.
Here at Yorba we've tried to do all of this for each bug that's ever
come in. But we now have over 800 open bugs and feature requests, which
is actually unsuprising given that Shotwell is a large program (96,000
lines of Vala code) with many thousands of users. So it's certainly
possible that some bugs in our database are no longer reproducible, or
are still poorly described, or no longer make sense given where Shotwell
is today.
If you're interested in looking at existing bugs to try to improve their
quality then you're very welcome to help out. Additional comments on
bugs are always welcome. It's probably best if you don't adjust bugs'
priorities or target milestones, though - we do that here at Yorba. You
can always add a comment to a bug saying "I think this bug should be a
higher priority" and if we agree we'll adjust the priority in response.
adam
_______________________________________________
Shotwell mailing list
[email protected]
http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell
