News for hackers. Stuff that matters.
Re:GitLab is down. Again. by reacharavindh on Thursday April 26, 2018 @10:41AM (#16932246)
Serious question: Would it be better if we had services that did not "move fast and break things"? particularly when dealing with user facing components like this?

Imagine a gitlab product that goes into operation, and gets updated with a good load of features every 3 or 6 months? The ones they replace with is thoroughly tested internally?

Re:GitLab is down. Again. by edjboston on Thursday April 26, 2018 @11:59AM (#16933058)
GitLab VPE here.

Historically the dominant source of outage minutes is indeed features that didn't scale (70%).

However, We've made great strides in the past 6 months on QA and release management and it's yielded a marked improvement in availability. The last week has been an exception to that.

We're in the midst of a move from Azure to GCP, and once that is done, we're going to rebuild out system to be entirely automated which will eliminate a class of manual mistakes.