Firefox

20479 readers

115 users here now

/c/firefox

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

Rules

1. Adhere to the instance rules

2. Be kind to one another

3. Communicate in a civil manner

Reporting

If you would like to bring an issue to the moderators attention, please use the "Create Report" feature on the offending comment or post and it will be reviewed as time allows.

founded 5 years ago

MODERATORS

k_o_t@lemmy.ml

golden_zealot@lemmy.ml

326

Firefox Development Is Moving From Mercurial To Git (groups.google.com)

submitted 2 years ago by pnutzh4x0r@lemmy.ndlug.org to c/firefox@lemmy.ml

32 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

[–] QuazarOmega@lemy.lol 52 points 2 years 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

[–] lemmyvore 36 points 2 years 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.

[–] ahriboy@kbin.social 2 points 2 years ago (1 children)

Mozilla should have their own Forgejo instance instead

[–] floridaman@lemmy.blahaj.zone 2 points 2 years 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.

[–] angrymouse@lemmy.world 1 points 2 years ago

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

[–] TWeaK@lemm.ee 0 points 2 years ago* (last edited 2 years 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.

[–] stolid_agnostic@lemmy.ml 4 points 2 years ago

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