ReleaseEngineering/Merge Duty: Difference between revisions

ReleaseEngineering/Merge Duty (view source)

29 bytes added , 5 February 2014

Confirmed users

4,971

edits

@@ Line 2: / Line 2: @@
 = Mergeduty =
-Mergeduty is responsible for performing branching + code uplifts, and making sure the automation is ready for those branches and merges.
+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?])
-* [[ReleaseEngineering/Merge Duty/Aurora will become an even numbered Gecko version]]
+* [[ReleaseEngineering/Merge Duty/Central will become an odd numbered Gecko version]]
-* [[ReleaseEngineering/Merge Duty/Aurora will become an odd numbered Gecko version]]
+* [[ReleaseEngineering/Merge Duty/Central will become an even numbered Gecko version]]
 Note that there are several uplifts involved:
@@ Line 12: / Line 12: @@
   central->aurora
   (every other)
   aurora->b2gXX_vX_X
-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.
+These may change, especially if we change the cadence to de-emphasize Aurora.
-Be sure to have a clear understanding of which patches are landing for which uplift.
 Duties include: