For a long time Firefox Desktop development has supported both Mercurial and Git users. This dual SCM requirement places a significant burden on teams which are already stretched thin in parts. We have made the decision to move Firefox development to Git.

  • We will continue to use Bugzilla, moz-phab, Phabricator, and Lando
  • Although we’ll be hosting the repository on GitHub, our contribution workflow will remain unchanged and we will not be accepting Pull Requests at this time
  • We’re still working through the planning stages, but we’re expecting at least six months before the migration begins
  • TWeaK@lemm.eeEnglish
    2·
    11 months ago

    So it’s not really moving from one to the other, it’s already on both and they’re closing the less popular one.

    • lemmyvore@feddit.nlEnglish
      1·
      11 months ago

      No. The primary source control is on Mercurial, with a Git interface. But since all patches must go through moz-phab (Phabricator) anyway the Git interface is basically read-only – you can use it to pull the code and you can use Git locally for your development, but you can’t use Git to push back into the main repo.

      Now the reference repository will switch from their own Mercurial infrastructure to a Github (Git) repository, but the flow will remain the same (Phabricator rather than GitHub pull requests). Nothing will change for devs who were using Git. Devs who were using Mercurial will have to switch to Git.

  • tempest@lemmy.ca
    1·
    11 months ago

    I always preferred mercurial as a user but all the tooling and everything else built in the last decade has been for git so it makes sense.

    • taladar@sh.itjust.works
      1·
      11 months ago

      Mercurial had a nice UI on messy internals. Git had an initially not quite that nice UI on solid internals. It is obvious why Git won in the end.

  • QuazarOmega@lemy.lol
    1·
    11 months ago

    Wierd that they’d switch to GitHub though, ideologically at least, I would think they’d host their own servers and, at most, have a mirror on GitHub

    • lemmyvore@feddit.nlEnglish
      1·
      11 months ago

      That’s basically what the GitHub repo will be, a mirror from which people can download the latest code. Mozilla dev flow does not use GitHub infrastructure and they don’t plan to.

    • TWeaK@lemm.eeEnglish
      0·
      11 months ago

      I think the trouble is when users start committing to git, they can’t really be mirrors because each one needs to combine the inputs from both. A mirror would be just a copy of one to the other, this is a constant merging exercise which requires significantly more effort.