ReleaseEngineering:MergeDuty: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
(Replaced content with "Moved to ReleaseEngineering/Merge_Duty")
 
(40 intermediate revisions by 4 users not shown)
Line 1: Line 1:
{{Release Engineering How To|Merge Duty}}
Moved to [[ReleaseEngineering/Merge Duty|ReleaseEngineering/Merge_Duty]]
 
= Mergeduty =
Mergeduty is responsible for making sure we're prepared for the next source code uplift. Merge duty bugs are assigned to the person on the point for current release.
 
Note that there are several uplifts involved:
beta->release
aurora->beta
central->aurora
 
For example, if mozilla-central currently contains Firefox 19, a bug may say "do xyz when FF19 merges to beta".  Wait for that uplift to happen, then have the bug owner land the patch.
 
Be sure to have a clear understanding of which patches are landing for which uplift.
 
Duties include:
* 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]
** [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]
* When we have nightlies from mozilla-central with the new version, update the bouncer location for [https://bounceradmin.mozilla.com/admin/mirror/location/9379/ firefox-nightly-latest] (installer) to use the new version
* 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
* [[ReleaseEngineering/How_To/Enable_or_Disable_Updates_on_Aurora#Enabling_Updates | Re-enable Aurora updates]]
 
= Next merge days =
 
https://wiki.mozilla.org/RapidRelease/Calendar
 
* {{Bug|842863}} Tracking bug for 02-apr-2013 migration work
* {{Bug|842864}} Tracking bug for 14-may-2013 migration work
* {{Bug|842865}} Tracking bug for 25-jun-2013 migration work
* {{Bug|842866}} Tracking bug for 06-aug-2013 migration work
* {{Bug|842868}} Tracking bug for 17-sep-2013 migration work
* {{Bug|842870}} Tracking bug for 29-oct-2013 migration work
* {{Bug|842872}} Tracking bug for 10-dec-2013 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.
 
= Future Merge Duty Bugs =
 
Move these under tracking bugs once they are created:
 
== ESR 17 EOL ==
* {{Bug|809314}} - Enable enable_pymake for ESR 17+

Latest revision as of 02:42, 5 February 2014

Moved to ReleaseEngineering/Merge_Duty

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