Skip to content
This repository has been archived by the owner on Jun 30, 2020. It is now read-only.

Add regression guidance #16

Closed
wants to merge 2 commits into from
Closed

Add regression guidance #16

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ff9bfd9
Add regression guidance
emceeaich Aug 29, 2018
a2c3994
Incorporating RelMan comments
emceeaich Sep 4, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
35 changes: 35 additions & 0 deletions policy/triage-bugzilla.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -59,6 +59,41 @@ Also, as a release approaches, the release status of open, high priority (P1) bu

An explanation of the release status field.

### Regressions

_A regression is a code change that degrades existing functionality or performance._

#### Is a regression

* Facebook homepage does not render
* Image elements do not appear in the DOM tree
* CSS Grid rules are not recognized
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • A new crash

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe also add an example of a performance regression, e.g. * Memory usage increased while typing in awesomebar.

* A new crash
* Memory usage increased while typing in awesomebar

#### Is not a regression

* A website dependent on an unimplented part of the CSS specification does not render as intended
* Firefox implements a feature differently than the user expects it to
* The reporter is requesting a new feature
* Refactoring code
* A bug that is not dependent on a code change in Firefox [but from external factors](https://bugzilla.mozilla.org/describecomponents.cgi?product=External%20Software%20Affecting%20Firefox) (e.g. a new crash caused by a Windows update, or a change in anti-virus software)

#### Handling regressions

If a bug has been reported with the `regression` keyword added, or the bug has the `regression` keyword, then:

* The commit which casued the regression should be found and noted in the bug
emceeaich marked this conversation as resolved.
Show resolved Hide resolved
* The bug will be reviewed at the [weekly regression triage meeting](https://wiki.mozilla.org/Platform#Weekly_Regression_Triage_Meeting)

Unless a bug is resolved as invalid, wontfix, or a duplicate; or if the bug is marked as P5, it is expected that the bug will refer to the commit that caused the regression.

If the commit which caused the regression has not been found, add the `regressionrange-wanted` keyword.

Once the regression range has been found, the `regressionrange-wanted` keyword should be removed, and the status flags for each affected release in the range of commits set to `affected`. The triage owner for the component may decide to set the status of a bug as `wontfix` for current and future versions.

If a bug is no longer considered a regression, the `regressionrange-wanted` keyword should be removed.

### Questions and Edge Cases

#### This bug is a feature request
Expand Down