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

APPROACH

In order to deliver gains into the hands of our engineers as early as possible, the work will be split into two components: developer-facing first, followed by piecemeal migration of backend infrastructure.

Phase One - Developer Facing

We’ll switch the primary repository from Mercurial to Git, at the same time removing support for Mercurial on developers’ workstations. At this point you’ll need to use Git locally, and will continue to use moz-phab to submit patches for review.

All changes will land on the Git repository, which will be unidirectionally synchronised into our existing Mercurial infrastructure.

Phase Two - Infrastructure

Respective teams will work on migrating infrastructure that sits atop Mercurial to Git. This will happen in an incremental manner rather than all at once.

By the end of this phase we will have completely removed support of Mercurial from our infrastructure.

  • RegalPotoo@lemmy.worldEnglish
    74·
    10 months ago

    … which is part of why they aren’t using GitHubs pull request feature to land changes?

        • Rustmilian@lemmy.world
          64·
          10 months ago

          It’s exactly what it means.

          “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 can all read it right there plan as day.
          If they weren’t planning to/considering it, then why specify “at this time”?
          I’m only a native English speaker, so guess I could be interpreting it wrong.
          Do tell oh wise one, what alternative meaning could it possibly have?

          Edit : statement from glob himself. 1000000728

          • Kogasa@programming.dev
            45·
            10 months ago

            I’m only a native English speaker, so guess I could be interpreting it wrong.

            You should try being a native English reader.

            What it means is “they will not be accepting pull requests at this time.” Whether or not they are open to changing this in the future is not specified. They have not specifically stated that this is off the table, nor have they stated this is their intent.

            • Rustmilian@lemmy.world
              44·
              10 months ago

              So they are considering it.
              Thanks for confirming my point.
              If they weren’t, they wouldn’t have specified, they’d just say “we will not be accepting Pull Requests”.

              You should try being a native English reader.

              Ironic

              • Kogasa@programming.dev
                42·
                10 months ago

                No. They’re just not publicly saying it’s off the table. Whether they’re entertaining it internally is a totally different question.

                • Rustmilian@lemmy.world
                  2·
                  10 months ago

                  What’s funny is I have direct contact with some of the internal Firefox devs. ◉⁠‿⁠◉
                  I’ll deadass just ask later.