Notes: "Triaging Bugs in GNOME"
Jul. 7th, 2009 11:43 am![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
marnanelIntroduction
About us: Tobias, Pedro
Motivation
We are here today to help people start triaging. Best way to learn a project.
Show best practices and common pitfalls.
Identify, discuss and solve current problems.
There are about 5 active triagers, but we get 800 bugs a week, 800 bugs get closed a week, and 7000 bugs are older than two years!
Bug triaging
Description
Basically triage is QA, managing bugs. Also, it makes users and developers happy.
GNOME methodology
Bugzilla is the bug DB; mature product, old and clunky
there is a mailing list, gnome-bugsquad at gnome.org
#bugs on GIMPnet
How do I triage bugs?
Join the mailing list;
read the triage guide on live.gnome.org
Write comments, ask on IRC or the mailing list
You can't get bug changing rights at the beginning; you have to say on the bugs what should happen and the dev is supposed to do it. Then when you've done that a few times you should ask on #bugs and get rights.
"Real triagers have more points than they are years old". (Note: marnanel has 17)
What do you do when you're triaging?
Be nice, friendly, happy
Answer early, often
Method
Adjust metadata; ask for stack trace; analyse it; look for dupes (use SDF); rename bug to include function, filename, location. Watch out for modules that don't like being triaged.
About us: Tobias, Pedro
Motivation
We are here today to help people start triaging. Best way to learn a project.
Show best practices and common pitfalls.
Identify, discuss and solve current problems.
There are about 5 active triagers, but we get 800 bugs a week, 800 bugs get closed a week, and 7000 bugs are older than two years!
Bug triaging
Description
Basically triage is QA, managing bugs. Also, it makes users and developers happy.
GNOME methodology
Bugzilla is the bug DB; mature product, old and clunky
there is a mailing list, gnome-bugsquad at gnome.org
#bugs on GIMPnet
How do I triage bugs?
Join the mailing list;
read the triage guide on live.gnome.org
Write comments, ask on IRC or the mailing list
You can't get bug changing rights at the beginning; you have to say on the bugs what should happen and the dev is supposed to do it. Then when you've done that a few times you should ask on #bugs and get rights.
"Real triagers have more points than they are years old". (Note: marnanel has 17)
What do you do when you're triaging?
Be nice, friendly, happy
Answer early, often
Method
Adjust metadata; ask for stack trace; analyse it; look for dupes (use SDF); rename bug to include function, filename, location. Watch out for modules that don't like being triaged.
