Confirmed users
586
edits
Platform/GFX/TriageSchedule: Difference between revisions
→Thoughts and comments about the first round: Some more comments
Msreckovic (talk | contribs) (Consolidate sections) |
(→Thoughts and comments about the first round: Some more comments) |
||
| Line 82: | Line 82: | ||
=== Thoughts and comments about the first round === | === Thoughts and comments about the first round === | ||
* (Milan) Worth revisiting the query for the bugs you've triaged a few days, or a week after you've reduced the number to zero - sometimes the new ones show up because of the component change or bug getting reopened, or some such. | * (Milan) Worth revisiting the query for the bugs you've triaged a few days, or a week after you've reduced the number to zero - sometimes the new ones show up because of the component change or bug getting reopened, or some such. | ||
* (Kats) Current method gives people exposure to other parts of the the code, but without sufficient context to properly triage bugs (no history of what landed recently, or if other similar bugs were reported in the past week). I would still prefer a component-watching approach | |||
* (Kats) Intermittents are more challenging to deal with - if it's a low-volume initially and later increases in volume who is responsible for it? | |||