Confirmed users
564
edits
Platform/GFX/TriageSchedule: Difference between revisions
Jump to navigation
Jump to search
→Process: More details
Msreckovic (talk | contribs) m (→Schedule: A few more rounds) |
Msreckovic (talk | contribs) (→Process: More details) |
||
| Line 16: | Line 16: | ||
** This is about asking for a regression range, or even getting one if you can reproduce the problem and you have time. | ** This is about asking for a regression range, or even getting one if you can reproduce the problem and you have time. | ||
** This is about CC-ing the people on the team (or elsewhere) you’re guessing could shed more light on the issue. | ** This is about CC-ing the people on the team (or elsewhere) you’re guessing could shed more light on the issue. | ||
** This is about doing an occasional needinfo, and should be reserved for what you deem is a high priority. | ** This is about doing an occasional needinfo, and should be reserved for what you deem is a high priority. | ||
=== Keywords === | |||
* Add the relevant keywords: | |||
** "crash" if it's a crash; | |||
** "hang" if it's a hang; | |||
** "perf" if it's a performance related issue; | |||
** "feature" if it's new code, doing something that wasn't done before; note that a "feature" can block a "crash", we want a wide definition; | |||
** "regression" - not quite sure about this, we may want to save it for really bad and immediate regressions only? | |||
* Clean up the bug: | |||
** set the correct platform if it's obvious and we're reasonably certain (e.g., DirectX issue is going to be Windows); | |||
** if we know how to reproduce it, set the "Has STR" field; if there is a regression range, set that as well. | |||
=== Schedule === | === Schedule === | ||