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

ReleaseEngineering/How To/Create new ESR branch (view source)

Revision as of 20:13, 16 July 2014

1,562 bytes added , 16 July 2014

→‎Testing

Rail

Confirmed users

3,104

edits

@@ Line 85: / Line 85: @@
    ln -s Darwin_x86_64-gcc3 Darwin_x86_64-gcc3-u-i386-x86_64
    ln -s Darwin_x86_64-gcc3 Darwin_x86-gcc3-u-i386-x86_64
+= Pull form mozilla-release =
+Once mozilla-release is merged form mozilla-beta you can run the script which pulls last changes form mozilla-release, updates some configs and replaces some branding bits.
+== Running gecko_migration.py for mozilla-esr ==
+'''EDIT''' configs/merge_day/release_to_esr.py and update ESR versions.
+Example invocation:
+ # clone mozharness
+ hg clone http://hg.mozilla.org/build/mozharness
+ python mozharness/scripts/merge_day/gecko_migration.py -c mozharness/configs/merge_day/release_to_esr.py
+* the script will tag mozilla-release
+* it will continue by pulling mozilla-release to mozilla-esrNN, adjusting branding and changing some configs.
+* Once the script finishes, run an hg diff to see the uncommitted changes that the script generated:
+ (cd build/mozilla-esrNN; hg diff) | more
+ # an |hg out| will show the migrated changesets; an |hg out --patch| will show the patches for the migrated changesets.
+* It's best to get a visual review by someone else as well.
+* Commit+push the final bits by
+ # Make sure you already pushed your release version bump and reconfiged before this part!
+ python mozharness/scripts/merge_day/gecko_migration.py -c mozharness/configs/merge_day/release_to_esr.py --commit-changes --push
+* The push should be available at https://tbpl.mozilla.org/?tree=Mozilla-EsrNN
+In case of failure, you can start again from the top; no need to clobber (the on-by-default clean-repos action will be sufficient).  It should be faster the second time, since you won't be pulling in as many changesets from hg.m.o.
 = Testing =