Change Details

In the tools/release repo we have two scripts that create branches: one for the tarball release (`branch.py`) and one for the train (`make-wmf-branch`). The train branch script is fairly inefficient, and `branch.py` is fairly efficient. We should merge these scripts, and favor the approach taken by `branch.py`. [x] Make `branch.py` push for both code review and directly to HEAD [x] CentralNotice branches from `wmf-deploy` rather than `master` -- will need to be accounted for somehow in `branch.py` [ ] Modifiy docs for adding an extension [ ] Wikitech-l email pointing to new docs

In the tools/release repo we have two scripts that create branches: one for the tarball release (`branch.py`) and one for the train (`make-wmf-branch`). The train branch script is fairly inefficient, and `branch.py` is fairly efficient. We should merge these scripts, and favor the approach taken by `branch.py`. [x] Make `branch.py` push for both code review and directly to HEAD [x] CentralNotice branches from `wmf-deploy` rather than `master` -- will need to be accounted for somehow in `branch.py` [x] Modifiy docs for adding an extension [ ] Wikitech-l email pointing to new docs

In the tools/release repo we have two scripts that create branches: one for the tarball release (`branch.py`) and one for the train (`make-wmf-branch`). The train branch script is fairly inefficient, and `branch.py` is fairly efficient. We should merge these scripts, and favor the approach taken by `branch.py`. [x] Make `branch.py` push for both code review and directly to HEAD [x] CentralNotice branches from `wmf-deploy` rather than `master` -- will need to be accounted for somehow in `branch.py` [ x] Modifiy docs for adding an extension [ ] Wikitech-l email pointing to new docs