Bug Triage

From MozillaWiki
(Redirected from Bugmasters)
Jump to: navigation, search
Last updated: 2017/12/08

Triage Process

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

Initiative Process

There are a number of workflows in Bugzilla that are in addition to and often across our Component system. These initiative will modify our Initiative Template and the modified document will be linked below. Any special tagging required by these initiates will be registered as Metadata and also described in the Initiative document.

  • Performance Initiative - Triage and tracking of bugs we believe are essential to Firefox's responsiveness and throughput. NOTE: Update of the Quantum Flow initiative.

Triage Scorecard

Triage status of unresolved bugs in Core, Firefox, Firefox Android, Firefox iOS, and Toolkit (excluding general and untriaged) without open needinfos filed since 2016-06-01

History is viewable as a Re:dash dashboard

Bug Farming

Automated cleanup of bugs is handled by the bug-husbandry-bot, under which regular and ad-hoc queries run.

Current Regular Queries

Intermittent Test Failure Cleanup

Closes bugs filed from Orange Factor for intermittent test failures. Intermittent test failure bugs which have had no new failures in 21 days (as measured by comment count) and have not been reopened in the past week are closed.

Other Requests

File a bug in the Bulk Bug Edit Requests component.

Release Cycle Queries and Activities

Move fix-optionals

1 week to release: mark all fix-optionals for upcoming release (beta) as wontfix and mark as affected for next release (nightly) (Query)

Stale Bug Reports

See also, the Chromium Project's automatic triage 'sheriffbot'.

Regular Triages

Core (was Platform) Regression Triage

Details on Platform wiki page (TODO: break out into module)

Firefox::General

Product Triage

Security Triage

Firefox 59 Queries

First nightly 2017-11-13

P1 bugs which are affecting or fix-optional for Firefox 59; these bugs should be reviewed to see if they are still P1s and if they should not be wontfixed.

Bugs for which we don't know if they affect Firefox 59 by triage status; un-triaged bugs should be reviewed as early in the cycle as possible.

Bugs filed later in the cycle should only be considered if they will result in a dot release if they are not addressed.

Triage stats for this release

Firefox 58 Queries

First nightly 2017-08-03

P1 bugs which are affecting or fix-optional for Firefox 58; these bugs should be reviewed to see if they are still P1s and if they should not be wontfixed.

Bugs for which we don't know if they affect Firefox 58 by triage status; un-triaged bugs should be reviewed as early in the cycle as possible.

Bugs filed later in the cycle should only be considered if they will result in a dot release if they are not addressed.

Triage stats for this release

Firefox 57 Queries

First Nightly: 2017-06-12

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
  • Triage Report - scoreboard for components with most un-triaged bugs

Office Hours

Wednesdays, alternating between 7 AM, Pacific and 5pm Pacific

In #bugmasters in IRC

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

Bugzilla Process and Rules