Account confirmers, Anti-spam team, Bureaucrats, canmove, Confirmed users, Module owners and peers, smwadministrator, smwcurator, Administrators, MozillaWiki team, Widget editors
731
edits
Release Management/Tracking rules: Difference between revisions
Jump to navigation
Jump to search
Release Management/Tracking rules (view source)
Revision as of 15:11, 10 February 2014
, 10 February 2014Add more stuff and improve the presentation
(+category) |
(Add more stuff and improve the presentation) |
||
| Line 12: | Line 12: | ||
= Not a regression = | = Not a regression = | ||
When dealing with new features, this case is common. | |||
If there is no patch | Tracking is recommended if: | ||
* The bug is a crash (or fix a crash) | |||
* Impact web compatibility | |||
* Add-on compatibility implications | |||
* Introduced a new feature which may need to be backed out | |||
If there is no patch on a critical bug report, the tracking is recommended. | |||
If the patch has already landed in Mozilla-central for a few days and an uplift requests has been filled (or already applied), tracking is not necessary (except for high risk changes). | If the patch has already landed in Mozilla-central for a few days and an uplift requests has been filled (or already applied), tracking is not necessary (except for high risk changes). | ||
[[category:Release_Management|T]] | [[category:Release_Management|T]] | ||