428
edits
Platform/GFX/TriageSchedule: Difference between revisions
Jump to navigation
Jump to search
adding WR triage notes
Jbonisteel (talk | contribs) (edits to the triage page) |
Jbonisteel (talk | contribs) (adding WR triage notes) |
||
| Line 40: | Line 40: | ||
* Consider the Severity value (blocker, critical, major, etc. under Importance) | * Consider the Severity value (blocker, critical, major, etc. under Importance) | ||
** If it's already set to anything higher than normal, please CC | ** If it's already set to anything higher than normal, please CC Jessie. | ||
** If you think it should be set to higher than normal, please do so, then CC | ** If you think it should be set to higher than normal, please do so, then CC Jessie. | ||
=== Schedule === | === Schedule === | ||
| 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. | ||
=== Old Feedback === | === 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. | |||
====For MVP==== | |||
These instructions apply specifically to triage for our MVP. Here is what you need to know about triaging bugs for the MVP: | |||
*What is our MVP? | |||
**WR Windows 10, Desktop, with NVIDIA graphics cards | |||
*When is it shipping? | |||
**It will officially ship with 67 (May 14th) | |||
**We are going to conduct an experiment in release for 66 (after March 19th) | |||
=====Triage buckets for the MVP===== | |||
These are bugs that we think are reasonable to fix and do not introduce significant risk to ship with our MVP in 67 | |||
P2 - 67: https://mzl.la/2Tl4Awv | |||
P3 - 67: https://mzl.la/2TrRcGU | |||
If you come across a bug during your triage that you suspect could be valuable for the MVP, ping Jeff or Jessie and we can help make that call. | |||
We also have a list for bugs we’d like to fix for 68: | |||
P2 - 68: https://mzl.la/2Uf6Ges | |||
====Non-MVP specific Bugs==== | |||
We want to continue shipping WR on various platforms throughout the year. Let's try and follow similar prioritization guidelines as our regular triage: | |||
*P1 - Must fix in order to release on specified platform (ie. intel, android, etc.) | |||
*P2 - Fix for the next release for specified platform | |||
*P3 - Backlog for specified platform platform | |||
*P4 - Don’t use | |||
*P5 - Won’t fix, but will accept patch | |||
We also have tracking bugs set up for some of the platforms we want to target and other important categories we want to track (such as performance). Please also add the appropriate tracking bug as you are doing your triage: | |||
wr-intel | |||
wr-android | |||
wr-android-mvp | |||
wr-mac | |||
wr-linux | |||
wr-perf | |||
wr-snap | |||
=== 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) 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? | * (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? | ||