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.

      • Kogasa@programming.dev
        33·
        10 months ago

        How does the opinion of your supposed internal contact at mozilla affect the basic English interpretation of the public announcement?

        • Rustmilian@lemmy.world
          42·
          10 months ago

          How does the opinion of your supposed internal contact at mozilla affect the basic English interpretation of the public announcement?

          We’d see who’s interpretation is right? Duh.

          Padenot (contributer with direct ties to Mozilla internal) agrees with me on GitHub PR being terrible. 🤣
          Waiting for other responses. 1000000723 1000000724

          Note : most of them are sleeping rn, so it’s going to take a bit of time.

          I asked Glob (the literal author of the announcement) directly as well. Waiting for him to wake up and see it, he was up at 3am last night, lol.

          • Kogasa@programming.dev
            33·
            10 months ago

            You’re quite the lunatic. I’m obviously not defending GitHub PRs, or saying Mozilla should or should not use them. I said “we are not open to PRs at this time” is not the same as “we will be open to PRs in the future.” The truth of that statement has absolutely nothing to do with whether or not Mozilla is, in fact, open to using PRs in the future. But there’s no point in telling you that, because you’re clearly unhinged. Have a good life.

            • Rustmilian@lemmy.world
              4·
              10 months ago

              First off :

              “we will be open to PRs in the future.”

              Is not what I said they meant to being with. I said planning/considering, which is wildly different.

              Second :
              Who’s unhinged? 1000000728 1000000729 Looks like I was right all along, they were indeed considering it but have since decided against it because of the same concerns I had mentioned previously. Is this definitive enough for you?