ReleaseEngineering/Merge Duty/Central will become an even numbered Gecko version

From MozillaWiki
Jump to: navigation, search


When a mozilla-central is an odd numbered Gecko version and will become an even numbered Gecko version, the B2G version on mozilla-central will stay, and the B2G version in mozilla-aurora will move to a mozilla-b2gXX_vX_X repo. For B2G 1.3, Gecko 28 moved from mozilla-aurora to mozilla-b2g28_v1_3.

See this bug.

Two weeks before

  • Read these docs. They're still fairly new as of Feb 7 2014, and they may not be 100% accurate or smooth yet. Please do your part to familiarize yourself with what needs doing.
  • Communicate with Release Management to determine what features are going to merge from central->aurora, aurora->beta, and which will be pref'ed off.

Release Merge Day

One week before

  • Release Merge Day + the release build will take up the first portion of this week.
  • Get the new B2G gecko branch live and green, if you haven't already.
  • Prep the patch for the other desktop train migrations
    • Look at blocking bugs against the merge day bugs, and ask around if there are any patches that need to land with the other migrations
  • Prep the other patches for Merge Day (next section). Merge Day will be Very Busy, so the patches+reviews beforehand will be very important.

Merge Day

dev.b2g newsgroup post

Like this:

Patches that are blocking-b2g:1.3+ should be landed there now. For more information, see the page below which always contains the latest information.

As a reminder, B2G v1.4 development remains on mozilla-central through the duration of the Gecko 30 development cycle due to end on March 17, so there is no change for where v1.4 patches are to land.

Post merge day

Update this documentation

The next person on mergeduty will appreciate it!