Release Management/B2G Landing: Difference between revisions

Release Management/B2G Landing (view source)

Revision as of 07:50, 16 January 2015

1,545 bytes added , 16 January 2015

Add 2.1S information

Styang

2

edits

@@ Line 233: / Line 233: @@
 * approval-gaia-v2.1? - http://mzl.la/1A21pFx
 * approval‑mozilla‑b2g34? - http://mzl.la/1yvEfe4
+=== v2.1S ===
+<b>Open for any feature work and bug fixes.</b>
+==== Source Repositories ====
+* Gecko: [http://hg.mozilla.org/releases/mozilla-b2g34_v2_1s/] ("b2g34_v2_1s")
+* Gaia: [https://github.com/mozilla-b2g/gaia/tree/v2.1s] ("v2.1s")
+* Manifest: [https://github.com/mozilla-b2g/b2g-manifest/tree/v2.1s] ("Manifest v2.1s")
+==== Landing Procedure ====
+* Patches must have blocking-b2g:2.1S+ to land.
+* Follow normal landing practices for Trunk/Master unless the but only affects the v2.1S branch.
+* Unless the bug only affects that branch, the bug must be Resolved/Fixed on master before uplifting.
+* Add a=2.1S+ to the end of the commit message and uplift to:
+** [https://github.com/mozilla-b2g/gaia/tree/v2.1s v2.1s]/[http://hg.mozilla.org/releases/mozilla-b2g34_v2_1s/] (setting status-b2g-v2.1S:fixed)
+* Bugs that also affect v2.1 (status-b2g-v2.1:affected) or v2.2 (status-b2g-v2.2:affected) will be handled on a case-by-case basis upon approval from release manager for uplift. Due to the specialized nature of this branch, <b>2.1S+ blocking status does not grant automatic approval</b> to uplift to v2.1 or v2.2. Patches must go through the regular approval process as detailed below for v2.1 or v2.2 consideration.
+* The v2.1 repos (b2g34 / v2.1) are regularly merged by the device team to the v2.1S branches. <b>Patches with v2.1 approval should not be double-landed on 2.1 and 2.1S branches.</b>
+==== Blocker Queries ====
+* All open blocking-b2g:2.1S? - http://mzl.la/17Ody9Z
+* All open blocking-b2g:2.1S+ - http://mzl.la/1IPWUlM
 === v2.2 ===