blob: 0a9dc3ad53f0633cdf79e5c0553b162b07d2a96e (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
|
Basic rules about triaging bugs for X.org:
* [[Bugs that are NEW and assigned to `xorg-team`|http://bugs.freedesktop.org/buglist.cgi?emailtype1=substring&emailassigned_to1=1&query_format=advanced&bug_status=NEW&email1=xorg-team%40lists.x.org]] are awaiting triage.
* [[ASSIGNED with owner set to `xorg-team`|http://bugs.freedesktop.org/buglist.cgi?emailtype1=substring&emailassigned_to1=1&query_format=advanced&bug_status=ASSIGNED&email1=xorg-team%40lists.x.org]] means that the bug is valid but not assigned to a specific developer yet
* ASSIGNED with owner changed to specific developer means that it's in that developer's queue
* Don't go closing bugs if they're assigned to someone else (including assigned to the team)
* Discuss a WONTFIX, NOTABUG, or NOTOURBUG with the developers first before closing any bug with these resolutions.
* General rules for the severity field:
* Blocker: server crashes, security problems, build problems with the default build, release issues.
* Critical: rendering errors, client-side crashes, (most) regressions.
* Use keywords intelligently:
* [[`want-backtrace`|http://bugs.freedesktop.org/buglist.cgi?keywords=want-backtrace&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=xorg]] on bugs that need a useful backtrace before they can be debugged
* change `want-backtrace` to [[`have-backtrace`|http://bugs.freedesktop.org/buglist.cgi?keywords=have-backtrace&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=xorg]] once you have one
* [[`regression`|http://bugs.freedesktop.org/buglist.cgi?keywords=want-backtrace&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=xorg]] for functionality regressions relative to previous releases
* [[`janitor`|http://bugs.freedesktop.org/buglist.cgi?keywords=janitor&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=xorg]] for cleanup or style tasks a la [[kernel janitors|http://janitor.kernelnewbies.org/]]
|