119
edits
(Add a "waiting to land" section heading to group the daily rebase/merge request and post-merge steps) |
(in case the sheriffs forget, check for the .arcconfig commit) |
||
Line 13: | Line 13: | ||
* Starting with a fresh clone of elm is recommended for each new chromium milestone. | * Starting with a fresh clone of elm is recommended for each new chromium milestone. | ||
hg clone --stream ssh://hg.mozilla.org/projects/elm | hg clone --stream ssh://hg.mozilla.org/projects/elm | ||
* Verify the first commit is the .arcconfig update. If the first commit doesn't look like "Bug xxx - FLOAT - REPO-elm - update .arcconfig repo callsign", run the following commands: | |||
./mach python dom/media/webrtc/third_party_build/restore_elm_arcconfig.py | |||
hg push -r tip | |||
== Update steps == | == Update steps == |
edits