Release Management/B2G Landing: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
m (-)
 
(408 intermediate revisions by 24 users not shown)
Line 1: Line 1:
= Pictoral Explanation =
#REDIRECT [[https://whattrainisitnow.com/calendar/]]
* [https://www.evernote.com/shard/s3/sh/f2da3da5-dd42-4ce7-9f83-6a6e282dcd53/55a2dbb926e97d5fac2d35f7adc5936b/res/cc34c7bf-1716-4ebd-b64f-9c592947e287/branching_and_landing-20130123-120420.jpg.jpg Click here]


= '''Current''' Codename/Version Mappings =
{{RELEASE_MANAGEMENT_OBSOLETE}}
* tef+ -> v1.0.0 (tagged close to FF18's release)
== Versions and Scheduling ==
* shira+ -> v1.0.1 (tagged close to FF19's release)
See also the [[RapidRelease/Calendar#B2G_Scheduling|Rapid Release calendar for B2G]].
* leo+ -> v1.1.0 (tagged close to FF20's release)


= Landings for B2G =
{| border="1" cellpadding="1"
== Until 1/25 ==
| '''FFOS Version'''
'''NOTE:''' For Gecko, all v1 landings must make it onto mozilla-central and "date" project branches. For Gaia, all v1 changes must land to master and the ongoing v1 branch ("v1-train").
| '''Scoping Complete ([https://wiki.mozilla.org/B2G/Roadmap Roadmap] updated)'''
| '''Release Availability '''
| '''Underlying Gecko Version'''
|-
| v2.5
| Jun 29, 2015
| November 2, 2015
|'''Gecko 44'''
|-
|}
<br>


=== v1.0.0 ===
=== Previous Releases ===
* Gecko: tip of [https://hg.mozilla.org/releases/mozilla-b2g18/ mozilla-b2g18]
* Gaia: v1.0.0 branch
* B2G Manifests: v1.0.0 branch (naming TBD)
* L10N: master


=== v1.0.1 ===
{| border="1" cellpadding="1"
* Gecko: [https://hg.mozilla.org/projects/date/ date project branch]
| '''FFOS Version'''
* Gaia: ongoing v1 branch (called "shira" right now, but changing to "v1-train" once repo migration completes)
| '''Scoping Complete'''
* B2G Manifests: ongoing v1 branch (naming TBD)
| '''Functional Complete (FC)'''
* L10N: master
| '''Code Freeze (CF)'''
| '''Underlying Gecko Version'''
| '''Included Gecko Security Fixes'''
| '''Blocking bug notation'''
| '''End-of-life (EOL)'''
| '''Final Tag'''
|-
|v1.0 (obsolete)
| n/a
| Dec 22, 2012
| January 2013
| Gecko 18
| Gecko 18
| blocking-basecamp:+, blocking-b2g:tef+
| -
| -
|-
|v1.0.1
| n/a
| Jan 15, 2013
| May 2013
| Gecko 18
| Gecko 20
| blocking-b2g:tef+, blocking-b2g:shira+
| -
| -
|-
|v1.1.0
| n/a
| Mar 29, 2013, with MMS/CBS/Auto-Correct waived
| July 2013
| Gecko 18+ (new APIs)
| Gecko 23
| blocking-b2g:leo+
| March 17, 2014
| -
|-
|v1.1.0hd
| n/a
| TBD
| TBD
| Same as 1.1.0 (merged automatically), with wvga
| Same as 1.1.0
| blocking-b2g:hd+
| March 17, 2014
| -
|-
|v1.2.0
| June 24, 2013
| Sep 16, 2013
| December 9, 2013
| Gecko 26
| Gecko 32
| blocking-b2g:koi+
| June 09, 2014
| -
|-
|v1.3.0
| September 16, 2013
| December 9, 2013
| <s>March 3, 2014</s> March 17, 2014
| Gecko 28
| Gecko 34
| blocking-b2g:1.3+
| September 01, 2014
| -
|-
| v1.4
| ~December 9, 2013
| Apr 29, 2014
| June 09, 2014
| Gecko 30
| Gecko 38+
| blocking-b2g:1.4+
| May 11, 2015
| -
|-
| v2.0
| ~Mar 17, 2014
| July 21, 2014
| Sep 01, 2014
| Gecko 32
| Gecko 39+
| blocking-b2g:2.0+
| July 29, 2015
| [https://hg.mozilla.org/releases/mozilla-b2g32_v2_0/rev/2e6f1d4deff9 B2G_2_0_END]
|-
| v2.1
| ~June 17, 2014
| October 13, 2014
| November 21, 2014
| Gecko 34
| Gecko 39+
| blocking-b2g:2.1+
| July 29, 2015
| [https://hg.mozilla.org/releases/mozilla-b2g34_v2_1/rev/41e10c6740be B2G_2_1_END]
|-
| v2.2
| ~Nov 24, 2014
| <s> April 06, 2015 </s> <br> April 29, 2015
|
|'''Gecko 37'''
|
|
|
|
|-
| v2.5
| ~Aug 2, 2015
|
|
|'''Gecko 44'''
|
|blocking-b2g:2.5+
|
|
|}


=== v2 and post-v1.0.1 work ===
* Gecko: tip of mozilla-central (post-v1.0.1 work will be uplifted)
* Gaia: master
* B2G Manifests: master
* L10N: master


== After 1/25 ==
See the [https://wiki.mozilla.org/B2G/Triage triage wiki page] for more info about remaining blocking bugs. See {{bug|829451}} for an explanation of the version scheme.
'''NOTE:''' For Gecko, all v1 landings must make it onto mozilla-central and tip of mozilla-b2g18. For Gaia, all v1 changes must land to master and the ongoing v1 branch ("v1-train").


=== v1.0.0 ===
== Nominating Issues ==
* Gecko: relbranch of [http://hg.mozilla.org/releases/mozilla-b2g18_v1_0_0 mozilla-b2g18_v1_0_0] (B2G_1_0_0_20130125190500)
See https://wiki.mozilla.org/B2G/Triage
* Gaia: v1.0.0 branch ("v1.0.0")
* B2G Manifests: v1.0.0 branch (naming TBD)
* L10N: master


=== v1.0.1 ===
== All about approval flags==
* Gecko: tip of [https://hg.mozilla.org/releases/mozilla-b2g18/ mozilla-b2g18]
see https://wiki.mozilla.org/Release_Management/Uplift_rules
* Gaia: ongoing v1 branch ("v1-train")
* B2G Manifests: ongoing v1 branch (naming TBD)
* L10N: master


=== v2 and post-v1.0.1 work ===
== Feature Landing Criteria ==
Same as above.


== After tagging 1.0.1rc1 ==
*Passes functional testing necessary to meet acceptance criteria
=== v1.0.0 ===
*Features must not land with device automated tests disabled
* Gecko: relbranch of [https://hg.mozilla.org/releases/mozilla-b2g18/ mozilla-b2g18] (TBD)
*No smoke-test, performance or checker boarding regressions
* Gaia: v1.0.0 branch ("v1.0.0")
*Includes integration/unit tests for features
* B2G Manifests: v1.0.0 branch ("v1-train")
*Performance/ stability metrics maintained at least at par with previous release
* L10N: TBD
*QA and release management must be informed of all complex feature landings before the landing occurs.
** Complex features:
***features that have a significant amount of risk wrt destabilizing the tree
***touches multiple modules
*NOTE: Partial landing of features is accceptable if they pass requisite tests and acceptance criteria
**Acceptance criteria met before being verified fixed by QA
**Acceptance criteria should include all necessary signoffs by UX, security,product and QA.


=== v1.0.1 ===
== Branch Information ==
* Gecko: relbranch of [https://hg.mozilla.org/releases/mozilla-b2g18/ mozilla-b2g18] (TBD)
See also [[B2G/Roadmap]].
* Gaia: v1.0.1 branch ("v1.0.1")
=== v2.5 ===
* B2G Manifests: v1.0.1 branch (naming TBD)
<b>Open for approved patches and security fixes.</b>
* L10N: master
==== Source Repositories ====
* Gecko: [http://hg.mozilla.org/releases/mozilla-b2g44_v2_5/] ("b2g44")
* Gaia: [https://github.com/mozilla-b2g/gaia/tree/v2.5 branch] ("v2.5")
* B2G Manifests: [https://github.com/mozilla-b2g/b2g-manifest/tree/v2.5 branch] ("v2.5")


=== v1.1.0 ===
==== Landing Procedure ====
* Gecko: tip of [https://hg.mozilla.org/releases/mozilla-b2g18/ mozilla-b2g18]
* 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‑b2g44+ / approval-gaia-v2.5+ to land (<b>including bugs marked as blocking-b2g:2.5+ or feature-b2g:2.5+</b>)
* Gaia: ongoing v1 branch ("v1-train")
** 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. <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>
* B2G Manifests: ongoing v1 branch (naming TBD)
* Follow normal landing practices for Trunk/Master.
* L10N: TBD
* Unless the bug only affects that branch, the bug must be Resolved/Fixed before uplifting.
* Add a=2.5+ for security bugs or a=<whoever approved> to the end of the commit message and uplift to:
** [https://github.com/mozilla-b2g/gaia/tree/v2.5 v2.5]/[http://hg.mozilla.org/releases/mozilla-b2g44_v2_5/ mozilla-b2g44_v2_5] (setting status-b2g-v2.5:fixed)


=== v2 and post-v1.1.0 work ===
==== Blocker/Approval Queries ====
Same as above.
* All blocking-b2g:2.5? - http://mzl.la/1HprZwt
* Open blocking-b2g:2.5+ - http://mzl.la/1Hps0R4
* approval-gaia-v2.5? - http://mzl.la/1Hps6rT
* approval‑mozilla‑b2g44? - http://mzl.la/1NrAoBG


== ... ==
=== v2.2 ===
More guidance once we get past these dates.
<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] ("b2g37")
* Gaia: [https://github.com/mozilla-b2g/gaia/tree/v2.2 2.2 branch] ("v2.2")
* B2G Manifests: [https://github.com/mozilla-b2g/b2g-manifest/tree/v2.2 2.2 branch] ("v2.2")


= Approvals =
==== Landing Procedure ====
* What doesn't need approval-mozilla-b2g18/approval-gaia-v1
* 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>)
** tef+ bugs can land directly on the current v1.0.0 branches (see above)
** 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. <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>
** shira+ bugs can land directly on the current v1.0.1 branches (see above)
* Follow normal landing practices for Trunk/Master.
** leo+ bugs can land on the appropriate v1.1.0 branches (see above)
* Unless the bug only affects that branch, the bug must be Resolved/Fixed before uplifting.
* What does need approval-mozilla-b2g18/approval-gaia-v1
* Add a=2.2+ for security bugs or a=<whoever approved> to the end of the commit message and uplift to:
** Bugs that aren't blocking-b2g plus'd
** [https://github.com/mozilla-b2g/gaia/tree/v2.2 v2.2]/[http://hg.mozilla.org/releases/mozilla-b2g37_v2_2/ mozilla-b2g37_v2_2] (setting status-b2g-v2.2:fixed)
** Approved bugs will land to Gecko mozilla-b2g18 tip and the ongoing v1 Gaia branch (to be picked up in the next tag)
* What we won't approve
** Bugs that aren't tracking-b2g18 plus'd


= Bug Flags =
==== Blocker/Approval Queries ====
* blocking-b2g:codename? is for CRITICAL bug fixes that we'd like to be considered for v1.0.0.0 after tomorrow
* All blocking-b2g:2.2? - http://mzl.la/1wabFce
* blocking-b2g:codename+ is for bugs that we've got agreement with partners about needing as part of the associated version
* Open blocking-b2g:2.2+ - http://mzl.la/1wabIou
* tracking-b2g18:+ ensures that it'll be on our radar for the v1 timeframe, and tracking-b2g18:? represents a nomination
* approval-gaia-v2.2? - http://mzl.la/1wabIVq
* tracking-b2g18:19+ ensures that it will be on our radar for the 6 weeks after v1.0 code ships (to be fixed prior to FF19's release). This flag will be used for security bugs fixed in FF19, for instance. Similarly, we'll be using 20+, 21+, etc.
* approval‑mozilla‑b2g37? - http://mzl.la/1BdXHfS


= Bug Status =
==== Latest Tagged Revision ====
* Bug resolution (Resolved/Fixed) applies specifically to mozilla-central
[http://hg.mozilla.org/releases/mozilla-b2g37_v2_2/rev/cefa70ef71e4 B2G_2_2_20150629_MERGEDAY]
* status-b2g18 represents the fix status on the Gecko/Gaia v1.* branches. '''Only set this flag once landed on all necessary branches, based upon the guide above'''


= Update Channels =
=== v2.2r ===
* Nightly/Beta channel users will receive updates for v1.0.0 until 1/25. After 1/25, they will receive updates to v1.{next released tag} until a time TBD
<b>Open for 2.2r blockers and approved patches.</b>
* A v2 Nightly channel will be created soon, at a time TBD
==== Source Repositories ====
* Gecko: [http://hg.mozilla.org/releases/mozilla-b2g37_v2_2r/ mozilla-b2g37_v2_2r] ("b2g37r")
* Gaia: [https://github.com/mozilla-b2g/gaia/tree/v2.2r 2.2r branch] ("v2.2r")
* B2G Manifests: [https://github.com/mozilla-b2g/b2g-manifest/tree/v2.2r 2.2r branch] ("v2.2r")
 
==== Landing Procedure ====
* Patches must have approval‑mozilla‑b2g37_v2_2r+, approval-gaia-v2.2r+, blocking-b2g:2.2r+, or feature-b2g:2.2r+ to land.
* Follow normal landing practices for Trunk/Master unless the bug only affects the v2.2r branch.
* Add a=2.2r+ for blockers/features or a=<whoever approved> to the end of the commit message and uplift to:
** [https://github.com/mozilla-b2g/gaia/tree/v2.2r v2.2r]/[http://hg.mozilla.org/releases/mozilla-b2g37_v2_2r/] (setting status-b2g-v2.2r:fixed)
* The v2.2 repos (b2g37 / v2.2) are regularly merged to the v2.2r branches. <b>Patches with v2.2 approval should not be double-landed on 2.2 and 2.2r branches.</b>
 
==== Blocker Queries ====
* All blocking-b2g:2.2r? - http://mzl.la/1Is4pmt
* Open blocking-b2g:2.2r+ - http://mzl.la/1JRVKGF
* approval-gaia-v2.2r? - http://mzl.la/1IKJOff
* approval‑mozilla‑b2g37_v2_2r? - http://mzl.la/1IKJU6o
 
==== Latest Tagged Revision ====
N/A
 
=== Trunk/Master (currently v2.6) ===
<b>Open for any feature work and bug fixes.</b>
Note that v2.6 (haven't branched, planned May/31) nightlies are generated from latest master as gaia and mozilla-central gecko
==== Source Repositories ====
* Gecko: [https://hg.mozilla.org/releases/mozilla-central mozilla-central] ("m-c")
* Gaia: [https://github.com/mozilla-b2g/b2g-manifest/tree/master master] ("master")
* B2G Manifests: [https://github.com/mozilla-b2g/b2g-manifest master] ("master")
==== Landing Procedure ====
* r+ is required
* For Gaia patches, land on [https://github.com/mozilla-b2g/gaia master] or set the checkin-needed bug keyword and it will be landed for you. Once landed, the bug should be marked RESOLVED FIXED.
* For Gecko patches, land on [https://hg.mozilla.org/integration/b2g-inbound/ b2g-inbound] or set the checkin-needed bug keyword and it will be landed for you.
** b2g-inbound is regularly merged by the [https://wiki.mozilla.org/Sheriffing sheriffs] to mozilla-central
** Bugs are automatically resolved once merged to mozilla-central.
 
==== Blocker Queries ====
* All blocking-b2g:2.6? - http://mzl.la/1Ng0SWB
* Open blocking-b2g:2.6+ - http://mzl.la/1Ng0Y0t
 
== Automatic Branch Uplifts ==
=== v2.2 ===
* Ready to uplift to mozilla-b2g37 (Gecko)
** <strike>[https://bugzilla.mozilla.org/buglist.cgi?order=cf_last_resolved&chfield=resolution&chfieldfrom=2015-01-12&bug_status=RESOLVED&bug_status=VERIFIED&resolution=FIXED&field0-0-0=cf_blocking_b2g&type0-0-0=anywordssubstr&value0-0-0=2.0%2B%202.1%2B%202.2%2B&field0-1-0=component&type0-1-0=nowords&value0-1-0=Gaia&field0-2-0=cf_status_b2g_2_2&type0-2-0=nowordssubstr&value0-2-0=fixed%20verified%20unaffected%20wontfix%20disabled&field0-3-0=status_whiteboard&type0-3-0=nowordssubstr&value0-3-0=NO_UPLIFT%20NPOTB%20POVB blocking-b2g:2.0+/2.1+/2.2+ (without NO_UPLIFT, NPOTB, or POVB)]</strike> - <b>ALL BLOCKERS MUST HAVE APPROVAL TO LAND</b>
** [https://bugzilla.mozilla.org/buglist.cgi?cf_last_resolved;field0-0-0=flagtypes.name;type0-0-0=anywordssubstr;value0-0-0=approval-mozilla-b2g37%2B;field0-1-0=cf_status_b2g_2_2;type0-1-0=nowordssubstr;value0-1-0=fixed%20verified%20unaffected%20wontfix%20disabled approval-mozilla-b2g37+]
* Ready to uplift to v2.2 (Gaia)
** <strike>[https://bugzilla.mozilla.org/buglist.cgi?f10=CP&o5=nowordssubstr&f1=OP&f8=component&f0=OP&v11=NO_UPLIFT%20NPOTB%20POVB&o11=nowordssubstr&resolution=FIXED&o2=anywordssubstr&f9=CP&j7=OR&f4=OP&v5=fixed%20verified%20unaffected%20wontfix%20disabled&chfieldto=Now&query_format=advanced&chfield=resolution&j1=OR&f3=CP&chfieldfrom=2015-01-12&f2=cf_blocking_b2g&chfieldvalue=FIXED&f11=status_whiteboard&bug_status=RESOLVED&bug_status=VERIFIED&j4=OR&f5=cf_status_b2g_2_2&v8=Gaia&f6=CP&v2=2.0%2B%202.1%2B%202.2%2B&f7=OP&o8=substring blocking-b2g:2.0+/2.1+/2.2+ (without NO_UPLIFT, NPOTB, or POVB)]</strike> - <b>ALL BLOCKERS MUST HAVE APPROVAL TO LAND</b>
** [https://bugzilla.mozilla.org/buglist.cgi?cf_last_resolved;field0-0-0=flagtypes.name;type0-0-0=anywordssubstr;value0-0-0=approval-gaia-v2.2%2B;field0-1-0=cf_status_b2g_2_2;type0-1-0=nowordssubstr;value0-1-0=fixed%20verified%20unaffected%20wontfix%20disabled approval-gaia-v2.2+]
* [https://bugzilla.mozilla.org/buglist.cgi?order=cf_last_resolved&resolution=FIXED&f1=bug_group&o1=substring&v1=sec&f2=cf_status_b2g_2_2&o2=equals&v2=affected Security bugs affecting v2.2]
 
=== v2.2r ===
* Ready to uplift to mozilla-b2g37r (Gecko)
** [https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&f1=status_whiteboard&o1=nowordssubstr&v1=NO_UPLIFT%20NPOTB%20POVB&f2=component&o2=nowordssubstr&v2=Gaia&f3=cf_status_b2g_2_2r&o3=nowordssubstr&v3=fixed%20verified%20unaffected%20wontfix%20disabled&f4=OP&j4=OR&f5=cf_blocking_b2g&o5=equals&v5=2.2r%2B&f6=cf_feature_b2g&o6=equals&v6=2.2r%2B&f7=CP blocking-b2g:2.2r+ or feature-b2g:2.2r+ (without NO_UPLIFT, NPOTB, or POVB)]
** [https://bugzilla.mozilla.org/buglist.cgi?cf_last_resolved;field0-0-0=flagtypes.name;type0-0-0=anywordssubstr;value0-0-0=approval‑mozilla‑b2g37_v2_2r%2B;field0-1-0=cf_status_b2g_2_2r;type0-1-0=nowordssubstr;value0-1-0=fixed%20verified%20unaffected%20wontfix%20disabled approval-mozilla-b2g37_v2_2r+]
* Ready to uplift to v2.2r (Gaia)
** [https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&f1=status_whiteboard&o1=nowordssubstr&v1=NO_UPLIFT%20NPOTB%20POVB&f2=component&o2=substring&v2=Gaia&f3=cf_status_b2g_2_2r&o3=nowordssubstr&v3=fixed%20verified%20unaffected%20wontfix%20disabled&f4=OP&j4=OR&f5=cf_blocking_b2g&o5=equals&v5=2.2r%2B&f6=cf_feature_b2g&o6=equals&v6=2.2r%2B&f7=CP blocking-b2g:2.2r+ or feature-b2g:2.2r+ (without NO_UPLIFT, NPOTB, or POVB)]
** [https://bugzilla.mozilla.org/buglist.cgi?cf_last_resolved;field0-0-0=flagtypes.name;type0-0-0=anywordssubstr;value0-0-0=approval-gaia-v2.2r%2B;field0-1-0=cf_status_b2g_2_2r;type0-1-0=nowordssubstr;value0-1-0=fixed%20verified%20unaffected%20wontfix%20disabled approval-gaia-v2.2r+]
* [https://bugzilla.mozilla.org/buglist.cgi?order=cf_last_resolved&resolution=FIXED&f1=bug_group&o1=substring&v1=sec&f2=cf_status_b2g_2_2r&o2=equals&v2=affected Security bugs affecting v2.2r]
 
== Sanity Checks ==
* FIXED 2.1+ blockers not 2.2:fixed - http://mzl.la/1wap4mS
* FIXED 2.2+ blockers not 2.2:fixed - http://mzl.la/1o0ZlaX
<!-- NOT NEEDED UNTIL 2.5 BRANCHES * FIXED 2.2+ blockers not 2.5:fixed - http://mzl.la/1GZsrmW -->
* FIXED 2.2+ blockers not master:fixed - http://mzl.la/1LUN5ps
<!-- NOT NEEDED UNTIL 2.5 BRANCHES * FIXED 2.5+ blockers not 2.5:fixed - http://mzl.la/1GO4uLW -->
* FIXED 2.5+ blockers not master:fixed - http://mzl.la/1dxpPC0
 
[[category:RelManArchive|B]]

Latest revision as of 11:52, 29 March 2023

Redirect to:

⚡ Warning: The content of this page is obsolete and kept for archiving purposes of past processes.

Versions and Scheduling

See also the Rapid Release calendar for B2G.

FFOS Version Scoping Complete (Roadmap updated) Release Availability Underlying Gecko Version
v2.5 Jun 29, 2015 November 2, 2015 Gecko 44


Previous Releases

FFOS Version Scoping Complete Functional Complete (FC) Code Freeze (CF) Underlying Gecko Version Included Gecko Security Fixes Blocking bug notation End-of-life (EOL) Final Tag
v1.0 (obsolete) n/a Dec 22, 2012 January 2013 Gecko 18 Gecko 18 blocking-basecamp:+, blocking-b2g:tef+ - -
v1.0.1 n/a Jan 15, 2013 May 2013 Gecko 18 Gecko 20 blocking-b2g:tef+, blocking-b2g:shira+ - -
v1.1.0 n/a Mar 29, 2013, with MMS/CBS/Auto-Correct waived July 2013 Gecko 18+ (new APIs) Gecko 23 blocking-b2g:leo+ March 17, 2014 -
v1.1.0hd n/a TBD TBD Same as 1.1.0 (merged automatically), with wvga Same as 1.1.0 blocking-b2g:hd+ March 17, 2014 -
v1.2.0 June 24, 2013 Sep 16, 2013 December 9, 2013 Gecko 26 Gecko 32 blocking-b2g:koi+ June 09, 2014 -
v1.3.0 September 16, 2013 December 9, 2013 March 3, 2014 March 17, 2014 Gecko 28 Gecko 34 blocking-b2g:1.3+ September 01, 2014 -
v1.4 ~December 9, 2013 Apr 29, 2014 June 09, 2014 Gecko 30 Gecko 38+ blocking-b2g:1.4+ May 11, 2015 -
v2.0 ~Mar 17, 2014 July 21, 2014 Sep 01, 2014 Gecko 32 Gecko 39+ blocking-b2g:2.0+ July 29, 2015 B2G_2_0_END
v2.1 ~June 17, 2014 October 13, 2014 November 21, 2014 Gecko 34 Gecko 39+ blocking-b2g:2.1+ July 29, 2015 B2G_2_1_END
v2.2 ~Nov 24, 2014 April 06, 2015
April 29, 2015 		Gecko 37
v2.5 ~Aug 2, 2015 Gecko 44 blocking-b2g:2.5+


See the triage wiki page for more info about remaining blocking bugs. See bug 829451 for an explanation of the version scheme.

Nominating Issues

See https://wiki.mozilla.org/B2G/Triage

All about approval flags

see https://wiki.mozilla.org/Release_Management/Uplift_rules

Feature Landing Criteria

  • Passes functional testing necessary to meet acceptance criteria
  • Features must not land with device automated tests disabled
  • No smoke-test, performance or checker boarding regressions
  • Includes integration/unit tests for features
  • Performance/ stability metrics maintained at least at par with previous release
  • QA and release management must be informed of all complex feature landings before the landing occurs.
    • Complex features:
      • features that have a significant amount of risk wrt destabilizing the tree
      • touches multiple modules
  • NOTE: Partial landing of features is accceptable if they pass requisite tests and acceptance criteria
    • Acceptance criteria met before being verified fixed by QA
    • Acceptance criteria should include all necessary signoffs by UX, security,product and QA.

Branch Information

See also B2G/Roadmap.

v2.5

Open for approved patches and security fixes.

Source Repositories

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‑b2g44+ / approval-gaia-v2.5+ to land (including bugs marked as blocking-b2g:2.5+ or feature-b2g:2.5+)
    • 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. 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.
  • Follow normal landing practices for Trunk/Master.
  • Unless the bug only affects that branch, the bug must be Resolved/Fixed before uplifting.
  • Add a=2.5+ for security bugs or a=<whoever approved> to the end of the commit message and uplift to:

Blocker/Approval Queries

v2.2

Open for approved patches and security fixes.

Source Repositories

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 (including bugs marked as blocking-b2g:2.2+ or feature-b2g:2.2+)
    • 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. 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.
  • Follow normal landing practices for Trunk/Master.
  • Unless the bug only affects that branch, the bug must be Resolved/Fixed before uplifting.
  • Add a=2.2+ for security bugs or a=<whoever approved> to the end of the commit message and uplift to:

Blocker/Approval Queries

Latest Tagged Revision

B2G_2_2_20150629_MERGEDAY

v2.2r

Open for 2.2r blockers and approved patches.

Source Repositories

Landing Procedure

  • Patches must have approval‑mozilla‑b2g37_v2_2r+, approval-gaia-v2.2r+, blocking-b2g:2.2r+, or feature-b2g:2.2r+ to land.
  • Follow normal landing practices for Trunk/Master unless the bug only affects the v2.2r branch.
  • Add a=2.2r+ for blockers/features or a=<whoever approved> to the end of the commit message and uplift to:
    • v2.2r/[2] (setting status-b2g-v2.2r:fixed)
  • The v2.2 repos (b2g37 / v2.2) are regularly merged to the v2.2r branches. Patches with v2.2 approval should not be double-landed on 2.2 and 2.2r branches.

Blocker Queries

Latest Tagged Revision

N/A

Trunk/Master (currently v2.6)

Open for any feature work and bug fixes. Note that v2.6 (haven't branched, planned May/31) nightlies are generated from latest master as gaia and mozilla-central gecko

Source Repositories

Landing Procedure

  • r+ is required
  • For Gaia patches, land on master or set the checkin-needed bug keyword and it will be landed for you. Once landed, the bug should be marked RESOLVED FIXED.
  • For Gecko patches, land on b2g-inbound or set the checkin-needed bug keyword and it will be landed for you.
    • b2g-inbound is regularly merged by the sheriffs to mozilla-central
    • Bugs are automatically resolved once merged to mozilla-central.

Blocker Queries

Automatic Branch Uplifts

v2.2

v2.2r

Sanity Checks

Retrieved from "https://wiki.mozilla.org/index.php?title=Release_Management/B2G_Landing&oldid=1245953"