428
edits
Platform/GFX/TriageSchedule: Difference between revisions
Jump to navigation
Jump to search
fixed some formatting of lists
Jbonisteel (talk | contribs) (adding WR triage notes) |
Jbonisteel (talk | contribs) (fixed some formatting of lists) |
||
| Line 66: | Line 66: | ||
These are bugs that we think are reasonable to fix and do not introduce significant risk to ship with our MVP in 67 | 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 | *P2 - 67: https://mzl.la/2Tl4Awv | ||
P3 - 67: https://mzl.la/2TrRcGU | *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. | 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. | ||
| Line 73: | Line 73: | ||
We also have a list for bugs we’d like to fix for 68: | We also have a list for bugs we’d like to fix for 68: | ||
P2 - 68: https://mzl.la/2Uf6Ges | *P2 - 68: https://mzl.la/2Uf6Ges | ||
====Non-MVP specific Bugs==== | ====Non-MVP specific Bugs==== | ||
| Line 87: | Line 87: | ||
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: | 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-intel | ||
wr-android | *wr-android | ||
wr-android-mvp | *wr-android-mvp | ||
wr-mac | *wr-mac | ||
wr-linux | *wr-linux | ||
wr-perf | *wr-perf | ||
wr-snap | *wr-snap | ||
=== Old Feedback on Process === | === 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? | ||