WebExtensions/AdvisoryGroup: Difference between revisions

 
Line 5: Line 5:
=Flow=
=Flow=


When a bug comes into WebExtensions, there is a multiple triage process. Advisory group is the location of last resort for when we need help. Before hand we would expect at least a bug to:
When a bug comes into WebExtensions, there is a multiple triage process. Advisory group is the location of last resort for when we need help. Before hand we would expect at least a bug to be triaged to see if its:
* Is a serious regression or blocker
* A bug that really doesn't need much discussion and can triaged quickly.
* A bug that needs more discussion, if so it will get marked [design-decision-needed]


Be marked with [design-decision-need] and talked about in the bi-weekly community meeting:
If it is marked with [design-decision-needed] it will be talked about in the community meeting.


* Mark a bug as [design-decision-needed], [https://mzl.la/2d73PBq existing bugs]
* If it sounds good it will get marked as [design-decision-approved], [https://mzl.la/2cXI6IH existing bugs]
* If it sounds good it will get marked as [design-decision-approved], [https://mzl.la/2cXI6IH existing bugs]
* Start sending in some patches for [design-decision-approved] bugs :)
* Someone needs to start sending in some patches for [design-decision-approved] bugs :)
* If we feel confident its not something we don't want to do,  sounds good it will get marked as [design-decision-denied] and marked as won't fix.
* If we still struggle with the bug, we'll mark it with [advisory-group]
* If we still struggle with the bug, we'll mark it with [advisory-group]


Confirmed users
1,158

edits