News for hackers. Stuff that matters.
Re:Scaling Mercurial at Facebook by thrownaway2424 on Wednesday January 08, 2014 @12:51AM (#7021948)
Immediate regressions are good! If someone at Google breaks my code, I will know within half an hour at the latest and I will tell them to go fix it or just revert their changes myself. Immediate regressions also go perfectly with daily (or hourly!) releases. If there's a performance problem it will be identified early and I will only have thousands of changes to investigate instead of tens of millions.

Imagine if I had a regression and I had to go to the other team saying "We just upgraded from the Foo you released 2 years ago to the one from last year and the performance sucks. Help!" I would not get any help. However I get plenty of support when I go to Foo-team to tell them that my Foo-per-second is 10% worse in the noon release compared to the midnight release.

Having artifacts and stable interfaces and library releases and all that is very ivory tower hocus pocus stuff. In practice instant integration is better.

Re:Scaling Mercurial at Facebook by Touche on Wednesday January 08, 2014 @08:03AM (#7023196)
I don't just mean performance regressions. Someone upstream can change an API in a way that doesn't fit well with your use-case, goes in and "fixes" your code (makes sure all the tests pass) to fit the new API but makes it less maintainable in the process.
Re:Scaling Mercurial at Facebook by thrownaway2424 on Wednesday January 08, 2014 @11:00AM (#7024264)
Teams (at Google) can't change calling code without the review and approval of the owners of the calling code, so what you state would not happen.