287
edits
Release Management/Tracking rules: Difference between revisions
Jump to navigation
Jump to search
→Not a regression: Request tracking: typo fix and minor update
m (→Release blocking issues: added telemetry/rev) |
(→Not a regression: Request tracking: typo fix and minor update) |
||
| Line 18: | Line 18: | ||
= Not a regression: Request tracking = | = Not a regression: Request tracking = | ||
Tracking requests are made by changing "tracking flags" -> "tracking-firefoxN" flag to "?" and updating "status- | Tracking requests are made by changing "tracking flags" -> "tracking-firefoxN" flag to "?" and updating "status-firefoxN" flag to "affected" on a bug in bugzilla. | ||
When dealing with new features, this case is common. | When dealing with new features, this case is common. | ||
Tracking is recommended if: | Tracking is recommended if: | ||
* You want to escalate quickly to get a fix in an important, unassigned bug. Relman will work to find an assignee. | * You want to escalate quickly to get a fix in an important, unassigned bug. Relman and engineering managers will work to find an assignee. | ||
* High volume crashes. For example, bugs with keyword ''topcrash*'' are usually tracked. | * High volume crashes. For example, bugs with keyword ''topcrash*'' are usually tracked. | ||
* High impact on web compatibility | * High impact on web compatibility | ||