Confirmed users
4,971
edits
ReleaseEngineering/Merge Duty: Difference between revisions
Jump to navigation
Jump to search
→Mergeduty
| Line 4: | Line 4: | ||
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]]) | 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 odd numbered Gecko version]] | ||
* [[ReleaseEngineering/Merge Duty/Central will become an even numbered Gecko version]] | * [[ReleaseEngineering/Merge Duty/Central will become an even numbered Gecko version]] | ||
| Line 15: | Line 16: | ||
These may change, especially if we change the cadence to de-emphasize Aurora. | These may change, especially if we change the cadence to de-emphasize Aurora. | ||
= Next merge days = | = Next merge days = | ||