Platform/GFX/TriageSchedule: Difference between revisions

remove references to gfx-noted; we just need to set the priority now
(Removed the explicit schedule, letting github.io page show it instead)
(remove references to gfx-noted; we just need to set the priority now)
Line 17: Line 17:
** 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.
** Some types of bugs would be handled outside of this triage process; for example, intermittent test errors can get a gfx-noted with a quick check if it's something obvious, not really spending time to resolve the issue if it takes a larger effort.
** Some types of bugs would be handled outside of this triage process; for example, intermittent test errors can get the priority set with a quick check if it's something obvious, not really spending time to resolve the issue if it takes a larger effort.


=== Keywords ===
=== Keywords ===
Line 33: Line 33:
** 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 (P1-P5 under importance) at the time that you make it gfx-noted.
* Set the priority field (P1-P5 under importance) at the time that you consider triaged. This will remove it from your queue.
** If you are not sure, set it to P3.
** 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, not a priority setting.
** 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, not a priority setting.
24

edits