MozillaWiki

ReleaseEngineering/Merge Duty

< ReleaseEngineering
Revision as of 02:40, 8 February 2014 by Asasaki (talk | contribs) (→‎Mergeduty)


Mergeduty

Mergeduty is responsible for performing branching + code uplifts, and making sure the automation is ready for those branches and merges. The steps that need to be performed alternate; we're basing this on whether mozilla-central will become an odd or even numbered Gecko version after Merge Day. (See: What train is it now? and RapidRelease/Calendar)

For the specific steps to run, see the following 2 pages:

Note that there are several uplifts involved: 

beta->release
aurora->beta
central->aurora
(every other)
aurora->b2gXX_vX_X

These may change, especially if we change the cadence to de-emphasize Aurora.

Next merge days

https://wiki.mozilla.org/RapidRelease/Calendar

  • bug 962187 Tracking bug for 17-mar-2014 migration work

Mergeduty should start looking at patches/owners the week before. NOTE: the tracking bugs themselves should NOT have patches in them. Dependent bugs should be filed for each thing that needs to be uplifted, and assigned to someone with the context to do it properly. Best practice: the patches are based on gecko_version so they get uplifted automatically.

Future Merge Duty Bugs

Move these under tracking bugs once they are created:

Retrieved from "https://wiki.mozilla.org/index.php?title=ReleaseEngineering/Merge_Duty&oldid=920475"