Confirmed users
1,345
edits
Performance/Project Candle: Difference between revisions
Jump to navigation
Jump to search
Performance/Project Candle (view source)
Revision as of 02:56, 21 September 2015
, 21 September 2015→Bug triage and tracking
Nnethercote (talk | contribs) |
Nnethercote (talk | contribs) |
||
| Line 28: | Line 28: | ||
== Bug triage and tracking == | == Bug triage and tracking == | ||
Bugs are prioritized via periodic triage threads on the mailing list | Bugs are prioritized via periodic triage threads on the mailing list. The process is described in the section below. | ||
If you want a bug that is related to power usage to be triaged on the mailing list, add "[Power]" to the bug whiteboard. After prioritization, this whiteboard marking will be changed to one of "[Power:P1]", "[Power:P2]", "[Power:P3]" or "[Power:meta]". The meaning of these markings, and links to all such bugs, is as follows. | If you want a bug that is related to power usage to be triaged on the mailing list, add "[Power]" to the bug whiteboard. After prioritization, this whiteboard marking will be changed to one of "[Power:P1]", "[Power:P2]", "[Power:P3]" or "[Power:meta]". The meaning of these markings, and links to all such bugs, is as follows. | ||
| Line 45: | Line 45: | ||
There is also a "power" keyword in Bugzilla, but this won't be used by Project Candle because the whiteboard annotations described above are more flexible. | There is also a "power" keyword in Bugzilla, but this won't be used by Project Candle because the whiteboard annotations described above are more flexible. | ||
== Bug triage process == | |||
These threads will have a title such as "Project Candle bug triage (7th September 2015)". The triage manager (currently nnethercote) will initiate these threads, listing each bug, asking relevant questions, and suggesting priorities. | |||
The primary purpose of these threads is to get eyes on bugs that have been marked with the "[Power]" whiteboard marking and to triage them. If we can also find people to do further investigation and/or assign themselves to a bug, even better, though that is not expected to happen with every bug. | |||
So please take a few minutes to look through the listed bugs. For each bug, decide if you agree with the suggested priority, and consider if you can add to the discussion in the bug, suggest somebody who might be able to work on it, or even take it on yourself. | |||
Note also that these email threads are substituting for face-to-face meetings where basic agreement can be achieved quickly and obviously. In contrast, on mailing lists it is harder to reach agreement like this, particularly because the bar for response is higher and it is traditional to avoid responding with simple "I agree" messages. Nonetheless, for these triage threads we specifically encourage this kind of response. In particular, if you agree with all the suggestions a simple "+1" response is helpful. Without such responses, it is likely that there will be few responses and the triage manager -- who took the time to write the message that starts the thread -- won't know if it's because (a) everybody agrees with their suggestions, or (b) nobody looked at the bugs, or (c) nobody cares, and this is discouraging. | |||
A few days later, after discussion has occurred, the triage manager will update the bugs appropriately. | |||
== Documentation and Tools == | == Documentation and Tools == | ||