Release Management/B2G Landing

From MozillaWiki
Jump to: navigation, search

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


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.1S

Open for 2.1S blockers 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 blocking-b2g:2.1S+ to land.
  • Follow normal landing practices for Trunk/Master unless the bug only affects the v2.1S branch.
  • Add a=2.1S+ to the end of the commit message and uplift to:
    • v2.1s/[1] (setting status-b2g-v2.1S:fixed)
  • Bugs that also affect 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, 2.1S+ blocking status does not grant automatic approval to uplift to v2.2. Patches must go through the regular approval process as detailed below for v2.2 consideration.

Blocker Queries

Latest Tagged Revision

B2G_2_1s_20150629_MERGEDAY

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.5)

Open for any feature work and bug fixes. Note that v2.5 (haven't branched, planned Nov/2) 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.1S

v2.2

v2.2r

Sanity Checks