Confirmed users
564
edits
Platform/GFX/TriageSchedule: Difference between revisions
Platform/GFX/TriageSchedule (view source)
Revision as of 18:49, 20 September 2016
, 20 September 2016Ps.
Msreckovic (talk | contribs) m (Through 2017 Q1.) |
Msreckovic (talk | contribs) m (Ps.) |
||
| Line 31: | Line 31: | ||
** set the correct platform if it's obvious and we're reasonably certain (e.g., DirectX issue is going to be Windows); | ** 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. | ** if we know how to reproduce it, set the "Has STR" field; if there is a regression range, set that as well. | ||
* Set the priority field at the time that you make it gfx-noted. | |||
** If you are not sure, set it to P3. | |||
** If *you* are going to fix it in this release, set it to P1. Note - this is not the same as thinking it *should* be fixed in this release. It's a scheduling note. | |||
** If *you* are going to fix it in the next release, set it to P2. Are you sure though? Do you know you will have time? | |||
** If you don't think we will ever have the time to spend on this, can ship for years without fixing it, and will take a patch if a contributor produces it, set it to P5. | |||
=== Schedule === | === Schedule === | ||