|
|
Line 28: |
Line 28: |
| How do we decide between P1, P2, and P3? Mike tried to balance the notion of "[[Compatibility/Severity_Triage|severity]]" with a sites impact (measured by popularity). The Trexa list is a good list to use to determine that: trexa.webcompat.com/lists | | How do we decide between P1, P2, and P3? Mike tried to balance the notion of "[[Compatibility/Severity_Triage|severity]]" with a sites impact (measured by popularity). The Trexa list is a good list to use to determine that: trexa.webcompat.com/lists |
|
| |
|
| ==== Webcompat Priority? bugs ====
| |
| [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=webcompat%3F&sharer_id=389500&list_id=14538489 Webcompat Priority? ] bugs are regularly triaged with the following outcomes:
| |
|
| |
| 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?cmdtype=dorem&remaction=run&namedcmd=webcompat-prio-p1&sharer_id=389500&list_id=14935238 [Webcompat Priority:P1<nowiki>]</nowiki>]: highest impact bugs or features for web compatibility
| |
| * [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=webcompat-p2&sharer_id=389500&list_id=14911122 [Webcompat Priority:P2<nowiki>]</nowiki>]: medium impact bugs of features for web compatibility
| |
| * [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=webcompat-p3&sharer_id=389500&list_id=14911142 [Webcompat Priority:P3<nowiki>]</nowiki>]: 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.
| |
|
| |
|
| ==== Untracked queries ==== | | ==== Untracked queries ==== |