3 ms·
Yes they did. They choose to scale out Mecurial to solve their problem. Wonder if they still use Mercurial? https://code.facebook.com/posts/218678814984400/sca
by mox1 10y ago
Yes they did. They choose to scale out Mecurial to solve their problem. Wonder if they still use Mercurial?
https://code.facebook.com/posts/218678814984400/scaling-mercurial-at-facebook/ https://code.facebook.com/posts/218678814984400/scaling-merc...
- jbergens 10y agoThey did a couple of months ago so I assume they still do.
- kyrra 10y agoBoth Facebook and Google are continuing to contribute to Mercurial, so they both have some vested interest in it. If you poke around the commits on the repo[0] you'll see commits from people with @fb.com and @google.com email addresses. The mailing lists also has activity from both companies still. As well, the Mercurial team does quarterly sprints (I believe), and Google is hosting the next one[1]. [0] https://www.mercurial-scm.org/repo/hg https://www.mercurial-scm.org/repo/hg [1] https://www.mercurial-scm.org/wiki/4.2sprint https://www.mercurial-scm.org/wiki/4.2sprint
- durin42 10y agoSprints are twice a year, once in the US and once in Europe.
- janwh 10y agoThey do. Durham Goode (Tech Lead on Source Control at Facebook) just held a talk at Git-Merge about how they scaled Mercurial at Fb. They seem to be quite happy with it, albeit applying quite a few restrictions on their internal users that are not really transferable to the general (outside-corporate) usage of VCS (for example only rebases are allowed, directly committing to master all the time, etc.)
- durin42 10y agoThat's actually pretty comparable to how we tend to operate the Mercurial project, FYI. We tend to prefer rebase to merge for feature work.