Bugmasters

From MozillaWiki
Jump to: navigation, search
Last updated: 2016/08/15

What we do

Mozilla's bugmaster develops policies and processes for managing bugs, their goal is to "leave no bug behind," and help Mozillians make crisp and actionable decisions on bugs, and enable them to follow-through on their decisions.

Triage Scorecard

All unresolved bugs in Core, Firefox, Firefox Android, Firefox iOS, Toolkit without open needinfos filed since 2016-06-01.

Untriaged This Release/Iteration Next Release/Iteration Backlog P4 (Not Used) Will Accept Patch Total Unresolved Firefox Bugs since 2016-06-01
3,407 156 420 848 36 97 4,964

Last update: 2016-08-15

Who we are

Projects

Code

  • Bugzilla Readable Statuses - enhancement to bugzilla.mozilla.com to help make the status of a bug more understandable
  • Triage Center - tool for finding untriaged bugs, and other bugs that need attention

Process

If you're triaging bugs in a component, Triage for Component Leads is the process we follow.

Meetings

The bugmaster office has no scheduled meetings at this time.

Communication

Get in touch with us. Don't hesitate to communicate using:

Useful Links

  • Triage Leads - who is responsible for triaging new bugs in each Firefox component
  • Bugmastering Guide - A guide helping on how to contribute to bug management and triage
  • Whiteboard tags - A list of common whiteboard field values and flags used in Bugzilla