550
edits
m (Emceeaich moved page Bugmasters/Projects/Bug Handling to Bug Triage/Projects/Bug Handling: Move to Bug Triage hiearchy.) |
|||
(9 intermediate revisions by the same user not shown) | |||
Line 9: | Line 9: | ||
==Triage Leads== | ==Triage Leads== | ||
We've [ | We've [[Bugmasters/Project/Bug Handling/Triage Leads|identified leads for 80% of these components]]. These people will be responsible for making sure new bugs landing in components, are acted on in a timely fashion, new bugs are now being moved into components by volunteers and Mozilla's contractors. Triage leads are encouraged to delegate the work to other members of their team, and set up rotations for reviewing bugs [see Networking]. | ||
In a separate project, another team is building groups of volunteers to help with classification of new bugs in a component. | In a separate project, another team is building groups of volunteers to help with classification of new bugs in a component. | ||
Line 29: | Line 29: | ||
Triage teams will have to follow up on these tags by hand during the pilot, and we expect bugs that are `btpp-fix-now` will be tracked by the team to confirm they are going into releases. | Triage teams will have to follow up on these tags by hand during the pilot, and we expect bugs that are `btpp-fix-now` will be tracked by the team to confirm they are going into releases. | ||
==Current Status== | |||
The [[Bugmasters/Process/Triage|new triage process]] is being presented at the 2016 London AllHands. | |||
Bugs are now displaying [https://www.npmjs.com/package/bugzilla-readable-status readable] triage statuses in bugzilla's new modal view (which will be become the default in Q3 2016.) | |||
==Next Step== | ==Next Step== | ||
In the third quarter we'll support teams as they start triaging bugs, and making more changes to bugzilla's UI to support triage. |