Confirmed users
4,971
edits
Release Management/Merge Documentation: Difference between revisions
Release Management/Merge Documentation (view source)
Revision as of 00:18, 23 October 2013
, 23 October 2013→Close the Trees
No edit summary |
|||
| Line 153: | Line 153: | ||
* Please use the "Remember previous state" option, so you can easily restore the previous status messages when you are finished (there will be a restore button at the bottom of the page). | * Please use the "Remember previous state" option, so you can easily restore the previous status messages when you are finished (there will be a restore button at the bottom of the page). | ||
* In order to change tree statuses, your browserID email needs to be added with sheriff permissions (ping edmorley/philor/catlee or ask in #developers). | * In order to change tree statuses, your browserID email needs to be added with sheriff permissions (ping edmorley/philor/catlee or ask in #developers). | ||
== Ping Release Engineering == | |||
Release Engineering will need to pause the hg-git sync to [http://git.mozilla.org/?p=releases/gecko.git;a=summary gecko.git]. If we don't pause that job, and we push the merges to central, aurora, and beta, we will most likely get the next gecko train's code into the wrong b2g versioned branch, and partners will have to deal with a non-fastforward commit. | |||
== Get Bhavana's Helper Script (do this every merge day) == | == Get Bhavana's Helper Script (do this every merge day) == | ||