Changes

Jump to: navigation, search

Release Management/B2G Landing

147 bytes removed, 16:25, 29 July 2015
tweak some v2.2 wording
<b>Open for approved patches and security fixes.</b>
==== Source Repositories ====
* Gecko: [http://hg.mozilla.org/releases/mozilla-b2g37_v2_2/ mozilla-b2g37_v2_2] ("mozilla-b2g37_v2_2b2g37")
* Gaia: [https://github.com/mozilla-b2g/gaia/tree/v2.2 v2.2 branch] ("v2.2")
* B2G Manifests: [https://github.com/mozilla-b2g/b2g-manifest/tree/v2.2 2.2] ("v2.2")
==== 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>)
** 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>
* Follow normal landing practices for Trunk/Master.
* Unless the bug only affects that branch, the bug must be Resolved/Fixed before uplifting.
Confirm
960
edits

Navigation menu