this post was submitted on 06 Nov 2023
327 points (99.4% liked)

Firefox

17811 readers
15 users here now

A place to discuss the news and latest developments on the open-source browser Firefox

founded 4 years ago
MODERATORS
[email protected]
327
Firefox Development Is Moving From Mercurial To Git (groups.google.com)
submitted 11 months ago by [email protected] to c/[email protected]
33 comments fedilink hide all child comments
 

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
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 53 points 11 months ago (4 children)

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

[–] [email protected] 37 points 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.

[–] [email protected] 2 points 11 months ago (1 children)

Mozilla should have their own Forgejo instance instead

[–] [email protected] 3 points 11 months ago

I love forgejo for Homelabbing purposes but Mozilla Foundation has the infrastructure to deploy something like GitLab, which has a much larger feature set compared to forgejo with more targeted toward the development work on large projects. But, Mozilla said the development flow would remain mostly the same as it is now, so most of the features in GitLab, Forgejo, or GitHub will remain unused.

[–] [email protected] 1 points 11 months ago

Yup, I noticed that too. But I got that you can't fight all the wars.

[–] [email protected] 0 points 11 months ago* (last edited 11 months ago) (1 children)

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.

[–] [email protected] 4 points 11 months ago

Downvotes without explanation as to why they think that doesn't make sense.