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: [http://whattrainisitnow.com/ What train is it now?] and [[RapidRelease/Calendar]])
For the specific steps to run, see the following 2 pages:
* [[ReleaseEngineering/Merge Duty/Central will become an odd numbered Gecko version]]
* [[ReleaseEngineering/Merge Duty/Central will become an even numbered Gecko version]]
These may change, especially if we change the cadence to de-emphasize Aurora.
Duties include:
* Create new hg bundles for affected repositories after the merges happen. (force build the bundle builders) (see {{bug|800280}})
** [http://buildbot-master57.srv.releng.use1.mozilla.com:8001/builders/mozilla-aurora%20hg%20bundle mozilla-aurora]
** [http://buildbot-master57.srv.releng.use1.mozilla.com:8001/builders/mozilla-beta%20hg%20bundle mozilla-beta]
** [http://buildbot-master57.srv.releng.use1.mozilla.com:8001/builders/mozilla-release%20hg%20bundle mozilla-release]
** [http://buildbot-master57.srv.releng.use1.mozilla.com:8001/builders/comm-aurora%20hg%20bundle comm-aurora]
** [http://buildbot-master57.srv.releng.use1.mozilla.com:8001/builders/comm-beta%20hg%20bundle comm-beta]
* [[ReleaseEngineering/How_To/Enable_or_Disable_Updates_on_Aurora#Enabling_Updates | Re-enable Aurora updates]]
** When re-enable updates for Aurora, update the bouncer locations for [https://bounceradmin.mozilla.com/admin/mirror/location/9380/ firefox-aurora-latest] (installer) and [https://bounceradmin.mozilla.com/admin/mirror/location/9717/ firefox-aurora-stub] (stub installer) to use the new version
** After bouncer update for nightly and aurora, check if disk space needs cleanup per {{bug|703559}}
= Next merge days =
