Engineering Workflow/Road Map: Difference between revisions

Jump to navigation Jump to search
(→‎Future: WIP: git support)
Line 96: Line 96:
=== Intent-to-land ===
=== Intent-to-land ===


=== cinnabar-less Git(Hub) gecko-dev support ===
=== Vanilla (cinnabar-less) Git support ===


git-cinnabar was created to allow developers to use Git to interact with Mercurial, mainly [https://hg.mozilla.org].  It has some downsides, however, such as being a bit tricky to install.  Ideally developers would be able to use vanilla Git to contribute to Firefox.
git-cinnabar was created to allow developers to use Git to interact with Mercurial, mainly [https://hg.mozilla.org|hg.mozilla.org].  It has some downsides, however, such as being a bit tricky to install.  Ideally developers would be able to use vanilla Git to contribute to Firefox.


If we view Phabricator and Lando as a conduit to getting code into mozilla-central, then ultimately VCS clients would only need to talk to Phabricator.  Phabricator natively supports both Mercurial and Git<ref>There is one wrinkle in supporting two VCSes for the same repository: like figuring out parent commits when a different VCS is used to pull down commits; see {{bug|1443375}} for how this was solved with git-cinnabar.</ref>
If we view Phabricator and Lando as a conduit to getting code into mozilla-central, then ultimately VCS clients would only need to talk to Phabricator.  Phabricator natively supports both Mercurial and Git<sup>[[#vcs-parent-note|1]]</sup>, and full Lando support means that developers will not need to talk to hg.mozilla.org directly.  We just need to ensure that the user experience of submitting a patch in progress to Try remains as straightforward as it is today.
 
Impact:
* No need to maintain nor educate people on git-cinnabar.
* End to unproductive VCS debates.
* Solidifies Phabricator-Lando as the conduit to hg.mozilla.org; this consolidation will make it easier to add more services and automation to the commit pipeline.
 
<div id="vcs-parent-note><small>
1. There is one wrinkle in supporting two VCSes for the same repository: like figuring out parent commits when a different VCS is used to pull down commits; see {{bug|1443375}} for how this was solved with git-cinnabar.</small></div>


<references />
=== Lando headless client API support ===
=== Lando headless client API support ===


Confirmed users
1,927

edits

Navigation menu