* [https://bugzilla.mozilla.org/enter_bug.cgi?product=Core&component=SVG SVG]
== Bug Triage and Whiteboard Tagging Process Guidelines ==
We use Please visit [https://bugzilla.mozilla.org Bugzilla] to track a combination of both bugs and new features. As such, we employ a hybrid system of Bugzilla priority and, optionally, a backlog tag (noted as <code>[layout:backlog:YYYYqQ]</code> in the bug's whiteboard field). The backlog tag, if provided, indicates the intended quarter and/or target release in which we intend to work on and ship a given feature. For instance, a tag of `[layout:backlog:2019q3Triage|our triage page]` indicates that we will attempt to work on the bug in Q3 of 2019. === Getting Started === Our [https://wiki.mozilla.org/Platform/Layout/Bugs bugs page] contains a list of useful links to Bugzilla queries we use for regular bug more information about our triage process and prioritization. === Priority === * '''Priority 1 (P1)''': Blockerguidelines, crash or very highas well as useful triage-impact performance or web compatibility related bug. Must-fix in the current iteration. The severity of the P1 should generally be set accordingly.* '''Priority 2 (P2)''': High-priority bug that should be in-progress and fixed within the next two releases. Includes moderately high-impact performance or web compatibility bugs.* '''Priority 3 (P3)''': Normal-priority bug or a backlog item.* '''Priority 4 (P4)''': Low-priority bug or managed by a bot (such as an intermittent test failure). We are unlikely to devote resources to these bugs any time soon.* '''Priority 5 (P5)''': We do not plan to spend time on these bugs but we will accept patchesqueries.
== Contributing ==
