ReleaseEngineering/How To/VCSSync: Difference between revisions

ReleaseEngineering/How To/VCSSync (view source)

Revision as of 19:33, 2 March 2016

447 bytes added , 2 March 2016

make easier to understand which are legacy processes and find docs

Hwine

Confirmed users

1,351

edits

@@ Line 3: / Line 3: @@
 This is documentation on the mozharness-based vcs sync processes.
-<b>See [http://people.mozilla.org/~hwine/tmp/vcs2vcs/ legacy docs] for the legacy process.</b>
+<div id="legacy"></div>
+<b>See [http://people.mozilla.org/~hwine/tmp/vcs2vcs/ legacy docs] for the legacy (aka "old") process.</b>
 = Quick notes =
@@ Line 231: / Line 232: @@
 == Maintenance ==
+=== How to add a repo to gecko-git ===
-=== How to add a repo to gecko-dev or gecko-git ===
+'''''CAUTION:''' production gecko.git is still handled by legacy vcs-sync - see [http://people.mozilla.org/~hwine/tmp/vcs2vcs/cookbook.html#adding-a-branch-to-gecko-git legacy docs].''<br />
-'''''CAUTION:''' production gecko.git is still handled by legacy vcs-sync - make changes there.''<br />
+This shouldn't be done lightly.  Gecko.git is our partner-oriented repo and should be treated with kid gloves.
-This shouldn't be done lightly.  Gecko.git is our partner-oriented repo and should be treated with kid gloves.  gecko-dev is our release-trains and inbound-branches only.
+=== How to add another repo to mirror for b2g OS ===
+Mirroring repositories for purpose of b2g os builds is handled by the legacy docs. See [http://people.mozilla.org/~hwine/tmp/vcs2vcs/cookbook.html#mirroring-a-git-repository here].
+=== How to add a repo to gecko-dev ===
+gecko-dev is our developer focused repository with all gecko branches related to release-trains and inbound-branches only.
 You should follow the example [http://hg.mozilla.org/build/mozharness/file/7d9425c91051/configs/vcs_sync/beagle.py#l96 here].  Annotated: