Release Management/B2G Landing

Pictoral Explanation

• Click here

Current Codename/Version Mappings

• tef+ -> v1.0.0 (tagged close to FF18's release)
• shira+ -> v1.0.1 (tagged close to FF19's release)
• leo+ -> v1.1.0 (tagged close to FF20's release)

Landings for B2G

Until 1/25

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

v1.0.0

• Gecko: tip of mozilla-b2g18
• Gaia: v1.0.0 branch
• B2G Manifests: v1.0.0 branch (naming TBD)
• L10N: master

v1.0.1

• Gecko: date project branch
• Gaia: ongoing v1 branch (called "shira" right now, but changing to "v1-train" once repo migration completes)
• B2G Manifests: ongoing v1 branch (naming TBD)
• L10N: master

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

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

• Gecko: mozilla-b2g18_v1_0_0 (B2G_1_0_0_20130125190500)
• Gaia: v1.0.0 branch ("v1.0.0")
• B2G Manifests: v1.0.0 branch (naming TBD)
• L10N: master

v1.0.1

• Gecko: tip of mozilla-b2g18
• Gaia: ongoing v1 branch ("v1-train")
• B2G Manifests: ongoing v1 branch (naming TBD)
• L10N: master

v2 and post-v1.0.1 work

Same as above.

After tagging 1.0.1rc1

v1.0.0

• Gecko: relbranch of mozilla-b2g18 (TBD)
• Gaia: v1.0.0 branch ("v1.0.0")
• B2G Manifests: v1.0.0 branch ("v1-train")
• L10N: TBD

v1.0.1

• Gecko: relbranch of mozilla-b2g18 (TBD)
• Gaia: v1.0.1 branch ("v1.0.1")
• B2G Manifests: v1.0.1 branch (naming TBD)
• L10N: master

v1.1.0

• Gecko: tip of mozilla-b2g18
• Gaia: ongoing v1 branch ("v1-train")
• B2G Manifests: ongoing v1 branch (naming TBD)
• L10N: TBD

v2 and post-v1.1.0 work

Same as above.

...

More guidance once we get past these dates.

Approvals

• What doesn't need approval-mozilla-b2g18/approval-gaia-v1
  • tef+ bugs can land directly on the current v1.0.0 branches (see above)
  • shira+ bugs can land directly on the current v1.0.1 branches (see above)
  • leo+ bugs can land on the appropriate v1.1.0 branches (see above)
• What does need approval-mozilla-b2g18/approval-gaia-v1
  • Bugs that aren't blocking-b2g plus'd
  • 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

• blocking-b2g:codename? is for CRITICAL bug fixes that we'd like to be considered for v1.0.0.0 after tomorrow
• blocking-b2g:codename+ is for bugs that we've got agreement with partners about needing as part of the associated version
• tracking-b2g18:+ ensures that it'll be on our radar for the v1 timeframe, and tracking-b2g18:? represents a nomination
• 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.

Bug Status

• Bug resolution (Resolved/Fixed) applies specifically to mozilla-central
• 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

• 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
• A v2 Nightly channel will be created soon, at a time TBD