Confirmed users
976
edits
Release Management/B2G Landing: Difference between revisions
Jump to navigation
Jump to search
Release Management/B2G Landing (view source)
Revision as of 01:55, 7 February 2015
, 7 February 2015→Landing Procedure
(Add 2.1S information) |
|||
| Line 263: | Line 263: | ||
==== Landing Procedure ==== | ==== Landing Procedure ==== | ||
* sec-high and sec-critical patches have automatic approval to land if the fix has landed on all affected Firefox branches. All others must have approval‑mozilla‑b2g37+ / approval-gaia-v2.2+ to land (<b>including bugs marked as blocking-b2g:2.2+ or feature-b2g:2.2+</b>) | * sec-high and sec-critical patches have automatic approval to land if the fix has landed on all affected Firefox branches. All others must have approval‑mozilla‑b2g37+ / approval-gaia-v2.2+ to land (<b>including bugs marked as blocking-b2g:2.2+ or feature-b2g:2.2+</b>) | ||
** If you have to land any | ** If you have to land any change, please make sure to validate your request with a strong reason to consider given the upcoming milestone and the release timeline. We request you to use approval-gaia-v2.2? for gaia and approval‑mozilla‑b2g37? for gecko to consider request uplift as necessary.<b> No guarantees on approval for non-blocking bugs, it may be granted depending on the risk/reward and how far we are in the release timeline </b> | ||
** The mozilla-aurora branch (currently tracking Gecko 37) will be automatically merged to mozilla-b2g37_v2_2 during this cycle. <b><u>There is no need to double-land patches on b2g37 if they have been approved for Aurora.</u></b> | ** The mozilla-aurora branch (currently tracking Gecko 37) will be automatically merged to mozilla-b2g37_v2_2 during this cycle. <b><u>There is no need to double-land patches on b2g37 if they have been approved for Aurora.</u></b> | ||
* Follow normal landing practices for Trunk/Master. | * Follow normal landing practices for Trunk/Master. | ||