Confirmed users
1,351
edits
ReleaseEngineering/How To/VCSSync: Difference between revisions
ReleaseEngineering/How To/VCSSync (view source)
Revision as of 21:49, 3 February 2016
, 3 February 2016fix oxford comma issue
(Added overview of goals) |
(fix oxford comma issue) |
||
| Line 12: | Line 12: | ||
#* All gecko primary development and release branches are merged into a single git repository (with CVS history) in "gecko-dev.git". | #* All gecko primary development and release branches are merged into a single git repository (with CVS history) in "gecko-dev.git". | ||
#* All gecko twig and misc branches are merged into a single git repository (with CVS history) in "gecko-projects.git". | #* All gecko twig and misc branches are merged into a single git repository (with CVS history) in "gecko-projects.git". | ||
# Support for Mozilla development tools and processes which (for operational or developer preference | # Support for Mozilla development tools and processes which (for operational needs (e.g. travis-ci), or developer preference, should appear in both Mercurial and Git repositories. | ||
#* These are "mirrors" from one system to the other. | #* These are "mirrors" from one system to the other. | ||
#* One repo is always designated the RoR (Repository of Record), and is the only one where commits will "stick". | #* One repo is always designated the RoR (Repository of Record), and is the only one where commits will "stick". | ||