canmove, Confirmed users
1,126
edits
Release Management/Uplift rules: Difference between revisions
→Special cases: Document standing arrangement with release drivers about a=testonly/a=npotb
(Move the Firefox (desktop + android) in a dedicated category) |
(→Special cases: Document standing arrangement with release drivers about a=testonly/a=npotb) |
||
| Line 72: | Line 72: | ||
* In the context of ''add-on SDK'' modifications, when an uplift is requested, it is normal not to find the land in m-c (because the m-c changeset is not posted in the bug report) | * In the context of ''add-on SDK'' modifications, when an uplift is requested, it is normal not to find the land in m-c (because the m-c changeset is not posted in the bug report) | ||
* If patches only make changes to tests, test harnesses or anything else that does not affect the shipped builds, they may land with self approval (use a=testonly, a=npotb etc). | |||
=Security fixes= | =Security fixes= | ||