Confirmed users
796
edits
Compatibility/WebCompat Priority Flags: Difference between revisions
Compatibility/WebCompat Priority Flags (view source)
Revision as of 17:54, 18 September 2020
, 18 September 2020→WebCompat Priority project flag: add some more descriptions around values
m (→webcompat tracking flag: update title) |
(→WebCompat Priority project flag: add some more descriptions around values) |
||
| Line 6: | Line 6: | ||
<br clear=all> | <br clear=all> | ||
The basic idea is as follows: | |||
1. The WebCompat team triages and diagnoses site compat bugs (generally reported by our users to webcompat.com). | |||
2. When they discover core interop bugs (as opposed to site bugs), they file a bug on Bugzilla, or identify an existing bug. | |||
3. The WebCompat Priority flag is set to "?" to nominate it for triage. Historically this has been done by Mike Taylor, with other Engineering Managers and Product Managers. | |||
4. The "?" bugs are triaged and given one of N values: | |||
* P1: This bug breaks either a lot of sites, or a top site. It should be fixed first. | |||
* P2: This bug breaks either a lot of sites, or a top site. It should be fixed next. | |||
* P3: This bugs breaks some sites, and should eventually get next. These bugs probably end up as P2s and P1s at some point. | |||
* revisit: This bug breaks a site, but it's either very long-tail or an edge case. Come back in case we discover this breaks more sites to get a higher priority. | |||
* -: Ideally this is never set because it seems rude. Clearing the flag for non-priorities seems like a better outcome. | |||
* ---: This clears the flag. Perhaps this is a performance or a UI issue, or something else entirely. Not really an interop bug. | |||
5. Somebody works with Engineering Managers to ensure these bugs are prioritized and fixed. | |||
6. Great success, promotions for everyone. 👑 | |||
==== Webcompat Priority? bugs ==== | ==== Webcompat Priority? bugs ==== | ||