330
edits
Release Management/Tracking rules: Difference between revisions
Release Management/Tracking rules (view source)
Revision as of 12:46, 11 February 2026
, Wednesday at 12:46Fix repo name
(remove obsolete section about fennec) |
Diannasmith (talk | contribs) (Fix repo name) |
||
| Line 32: | Line 32: | ||
If there is no patch on a critical or high-impact bug report, then tracking is recommended. | If there is no patch on a critical or high-impact bug report, then tracking is recommended. | ||
If the patch has already landed in | If the patch has already landed in firefox-main for a few days and an uplift request has been filled (or already applied), tracking is not necessary (except for high risk changes). | ||
What does it mean for a bug to be tracked? Release management will triage it about once a week, will follow up with developers, QE, managers, project managers, and product teams to get it fixed, tested, and in affected releases as soon as possible. | What does it mean for a bug to be tracked? Release management will triage it about once a week, will follow up with developers, QE, managers, project managers, and product teams to get it fixed, tested, and in affected releases as soon as possible. | ||