Compatibility/WebCompat Priority Flags: Difference between revisions
m (→webcompat tracking flag: add a TODO) |
(→webcompat tracking flag: WIP edits) |
||
| Line 3: | Line 3: | ||
A Bugzilla webcompat tracking flag exists. Its purpose is to put interop and compat bugs on the radar, to be triaged and prioritized accordingly. | A Bugzilla webcompat tracking flag exists. Its purpose is to put interop and compat bugs on the radar, to be triaged and prioritized accordingly. | ||
==== webcompat? bugs ==== | |||
[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=webcompat%3F&sharer_id=389500&list_id=14538489 webcompat? ] bugs are regularly triaged with the following outcomes: | [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=webcompat%3F&sharer_id=389500&list_id=14538489 webcompat? ] bugs are regularly triaged with the following outcomes: | ||
1. [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=runnamed&namedcmd=webcompat%2B webcompat+] is | 1. [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=runnamed&namedcmd=webcompat%2B webcompat+] is set and a priority is assigned to one of the following whiteboard tags, depending on the number of affected sites (or dupes), or how the issue affects top sites or other strategic initiatives. | ||
* [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=%5Bwebcompat%3Ap1%5D&list_id=14462197 [webcompat:p1<nowiki>]</nowiki>]: highest impact bugs or features for web compatibility | * [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=%5Bwebcompat%3Ap1%5D&list_id=14462197 [webcompat:p1<nowiki>]</nowiki>]: highest impact bugs or features for web compatibility | ||
| Line 16: | Line 17: | ||
TODO: add queries that don't have [webcompat-revisit], and only have [webcompat-revisit]. | TODO: add queries that don't have [webcompat-revisit], and only have [webcompat-revisit]. | ||
WIP queries: | |||
* [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=layout-webcompat%3F&sharer_id=389500&list_id=14673759 layout webcompat? bugs] | |||
[[Category:Web Compatibility]] | [[Category:Web Compatibility]] | ||
Revision as of 16:58, 18 April 2019
webcompat tracking flag
A Bugzilla webcompat tracking flag exists. Its purpose is to put interop and compat bugs on the radar, to be triaged and prioritized accordingly.
webcompat? bugs
webcompat? bugs are regularly triaged with the following outcomes:
1. webcompat+ is set and a priority is assigned to one of the following whiteboard tags, depending on the number of affected sites (or dupes), or how the issue affects top sites or other strategic initiatives.
- [webcompat:p1]: highest impact bugs or features for web compatibility
- [webcompat:p2]: medium impact bugs of features for web compatibility
- [webcompat:p3]: low impact bugs or features for web compatibility (but still considered important).
2. The tracking flag is left alone. The intention is to keep potentially important issues on our radar by not removing the flag — as we become aware of more site breakage it will be re-triaged and prioritized accordingly.
3. The tracking flag is cleared. This probably means the issue is not considered a compatibility issue.
TODO: add queries that don't have [webcompat-revisit], and only have [webcompat-revisit].
WIP queries: