ReleaseEngineering/How To/Create new ESR branch: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Created page with "{{Release Engineering How To|Create new ESR branch}} ESR17 process was tracked by {{Bug|796995}} and the dependent bugs. The process can be split into 2 major parts: internal an...")
 
(Replaced content with "The documentation has been moved to [https://github.com/mozilla/releasewarrior/blob/master/how-tos/new-esr-branch-setup.md releasewarrior]")
 
(38 intermediate revisions by 9 users not shown)
Line 1: Line 1:
{{Release Engineering How To|Create new ESR branch}}
The documentation has been moved to [https://github.com/mozilla/releasewarrior/blob/master/how-tos/new-esr-branch-setup.md releasewarrior]
 
ESR17 process was tracked by {{Bug|796995}} and the dependent bugs. The process can be split into 2 major parts: internal and external
 
= Internal changes =
This covers changes to configs, buildbotcustom and tools.
 
[https://bugzilla.mozilla.org/attachment.cgi?id=678768&action=edit buildbotcustom changes] for ESR17 were not critical and are not ESR specific.
 
== tools changes ==
[https://bugzilla.mozilla.org/attachment.cgi?id=678767&action=edit tools changes]
* adds new release branch to [http://hg.mozilla.org/build/tools/file/default/buildfarm/maintenance/production-masters.json production-masters.json] file
* adds new branch to buildapi's [http://hg.mozilla.org/build/tools/file/default/buildfarm/maintenance/production-branches.json production-branches.json] file
* since the [https://bugzilla.mozilla.org/attachment.cgi?id=678814&action=edit config patch] introduces new configurations file which are need to be symlinked to the build/scheduler master there is a need for a fabric methos to create the links
* mozconfig whitelist changes (tested in {{bug|808077}})
* preproduction tweks
 
== buildbot-configs changes ==
Some highlights:
* Explicitly list the platforms (and use lock_platforms) since we don't ship ESR to all mozilla-central/release platforms (android, for example)
* Copy mozilla-beta configs, compare them to the previous ESR release and check if you understand what they stand for
* No dep/nightly L10N builds required, as a result no need to create Tinderbox trees
* check mozilla-beta exceptions (loops) and check if they are aplicable to the current ESR
* for every exception (MERGE DAY exceptions) file a bug to track it
=== New release configs ===
* Make sure that the following variables set
releaseConfig['partialUpdates'] = {}
releaseConfig['skip_updates'] = True
releaseConfig['verifyConfigs'] = {}
releaseConfig['ftpSymlinkName'] = 'latest-esr'
* File new tracking bug for the next minor esr release (17.0.1esr) to update these variables
* update previous release configs and set
releaseConfig['ftpSymlinkName'] = 'latest-10.0esr'
* add mozilla2/*/comm-esr17/release/l10n-mozconfig for every platform. Copy them from mozilla-beta and compare to the previous esr configs
* add mozilla2/linux/comm-esr17/release/mozconfig (linux only). We need this for source builder. Will be fixed by {{bug|748796}}

Latest revision as of 04:58, 9 March 2017

The documentation has been moved to releasewarrior