ReleaseEngineering/Merge Duty: Difference between revisions

ReleaseEngineering/Merge Duty (view source)

571 bytes removed , 8 February 2014

Confirmed users

4,971

edits

@@ Line 17: / Line 17: @@
 Duties include:
-* After the Feb 4 merge day, the actual train merges are on Release Engineering to perform.
-* Bumping the [https://hg.mozilla.org/build/buildbot-configs/file/97b9e0b83e84/mozilla/master_common.py#l226 gecko_version of main repositories]. With {{bug|884074}} now landed, this replaces the "MERGE DAY" comments that we used to go through by hand.
-* The week before uplift, contact owners for all of the above to make a final decision of which bits should be uplifted or not.
-* Coordinate landing of all the merge patches with owners. Coordinate deployment with buildduty.
 * 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]