428
edits
Platform/GFX/TriageSchedule: Difference between revisions
Jump to navigation
Jump to search
more small formatting edits
Jbonisteel (talk | contribs) (more small edits) |
Jbonisteel (talk | contribs) (more small formatting edits) |
||
| Line 49: | Line 49: | ||
See [https://firefoxgraphics.github.io/graphicstriage/ dashboard] for the schedule and current counts. | See [https://firefoxgraphics.github.io/graphicstriage/ dashboard] for the schedule and current counts. | ||
=== WebRender Triage | ====Old Feedback on Process==== | ||
* (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? | |||
==WebRender Triage== | |||
As of March 2019, we are going to include the WebRender component in our regular triage process. This provides guidelines for how to do triage for WebRender. | As of March 2019, we are going to include the WebRender component in our regular triage process. This provides guidelines for how to do triage for WebRender. | ||
| Line 94: | Line 98: | ||
*wr-perf | *wr-perf | ||
*wr-snap | *wr-snap | ||