Confirmed users
1,351
edits
ReleaseEngineering/How To/Create new ESR branch: Difference between revisions
Jump to navigation
Jump to search
ReleaseEngineering/How To/Create new ESR branch (view source)
Revision as of 23:55, 3 June 2013
, 3 June 2013sometimes need to shorten branch names
(update tree status additions) |
(sometimes need to shorten branch names) |
||
| Line 23: | Line 23: | ||
* check mozilla-beta exceptions (loops) and check if they are aplicable to the current ESR | * 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 | * for every exception (MERGE DAY exceptions) file a bug to track it | ||
* you may need to add shortening code for new branches | |||
** be sure to run <tt>test-masters.sh</tt> to verify | |||
** see, e.g. https://hg.mozilla.org/build/buildbotcustom/annotate/b863ef3d9559/common.py#l128 | |||
=== New release configs === | === New release configs === | ||
* Make sure that the following variables set | * Make sure that the following variables set | ||