Release Management/B2G Landing: Difference between revisions

Release Management/B2G Landing (view source)

1,378 bytes removed , 12 January 2015

Removing 1.3T at this point

Confirmed users

976

edits

@@ Line 153: / Line 153: @@
 == Branch Information ==
 See also [[B2G/Roadmap]].
-=== v1.3T ===
-<b>Open for 1.3T+ blockers.</b>
-==== Source Repositories ====
-* Gecko: [https://hg.mozilla.org/releases/mozilla-b2g28_v1_3t mozilla-b2g28_v1_3t] ("b2g28_v1_3t")
-* Gaia: [https://github.com/mozilla-b2g/gaia/tree/v1.3t v1.3t branch] ("v1.3t")
-==== Landing Procedure ====
-* Patches must have blocking-b2g:1.3T+ to land.
-* Follow normal landing practices for Trunk/Master unless the but only affects the v1.3T branch.
-* Unless the bug only affects that branch, the bug must be Resolved/Fixed before uplifting.
-* Add a=1.3T+ to the end of the commit message and uplift to:
-** [https://github.com/mozilla-b2g/gaia/tree/v1.3t v1.3t]/[https://hg.mozilla.org/releases/mozilla-b2g28_v1_3t b2g28_v1_3t] (setting status-b2g-v1.3T:fixed)
-* Bugs that also affect v1.4 (status-b2g-v1.4:affected) will be handled on a case-by-case basis for uplift. Due to the specialized nature of this branch, <b>1.3T+ blocking status does not grant automatic approval</b> to uplift to v1.4. Patches must go through the regular approval process as detailed below for v1.4 consideration.
-* The v1.3 repos (b2g28 / v1.3) are regularly merged by sheriffs to the v1.3t branches. <b>Patches with v1.3 approval should not be double-landed on the two branches.</b>
-==== Blocker/Approval Queries ====
-* All blocking-b2g:1.3T? - http://mzl.la/1gQENSU
-* Open blocking-b2g:1.3T+ - http://mzl.la/1gQF2gP
 === v1.4 ===