We're also excited that they are open core: https://news.ycombinator.com/item?id=18117755
BTW There is a spelling mistake in the title Sourcepgrah => Sourcegraph
12,257 karma · joined December 15, 2009
We're also excited that they are open core: https://news.ycombinator.com/item?id=18117755
BTW There is a spelling mistake in the title Sourcepgrah => Sourcegraph
We measure efficiency by measuring the MR rate, the number of merge requests in a month devided by the number of engineers. To game the number you have to split work up in smaller Parts which helps cycle time, coordination, predictability, and quality, for example smaller changes are easier to review.
Real-time collaboration with text is so essential that this weekend I worked on a proof of concept with a friend to bring it to Gitlab issues https://gitlab.com/gitlab-org/gitlab/-/issues/21473#note_301...
BTW We're trying to bring real-time collaboration to GitLab issues so you can do the same in GitLab. I spend some time on that this weekend https://gitlab.com/gitlab-org/gitlab/-/issues/21473#note_301...
Edit: The twitter thread from the author is a great summary of Redwood and its benefits https://twitter.com/mojombo/status/1237441122097487873
The update article mentions it was meant for versioned software.
I tried to articulate the various levels of branching you need in GitLab Flow https://docs.gitlab.com/ee/topics/gitlab_flow.html The various levels are: feature branches, production branches, environment branches, and release branches.
I'm glad we did and today GitLab has a big monolith but also a ton of services working together https://docs.gitlab.com/ee/development/architecture.html#com...
I did an interview about this yesterday https://www.youtube.com/watch?v=WDqGaPGBZ9Y
BTW Gartner now has an online review tool called Peer Insights https://www.gartner.com/en/products/peer-insights Here you can read the customer reviews https://www.gartner.com/reviews/market/application-release-o... I might be a bit biased because in 2018 GitLab won Gartner their customer choice award and recently we won another awards based on peer insights https://about.gitlab.com/press/releases/2019-07-26-gitLab-re...
An important thing these firms do is aggregate customer feedback. For a consumer tool I can look on Quora and for a development tool I can look at Hacker News. But for enterprise tools the people that use the product are often not allowed to share feedback themselves. However they are allowed to talk with analysts.
That is why the opinions of these analysts are often really important to convince new customers your product is any good https://about.gitlab.com/is-it-any-good/
BTW We just won a 451 Firestarter award https://about.gitlab.com/press/releases/2020-01-14-gitlab-re... which we're stoked about.
Sent: 20 February 2017 12:22 To: r 13)boeinn com> Subject: REr—r. 777 ECL COC update request Fly home today — having the kitchen replaced on Thursday through to Friday next week L Amazing what a brown envelope can achieve — it isn't anywhere near as good as it would appear to be reading the report. The FAA were neither thorough nor demanding and failed to write up marry issues. And the lies, the damned lies — I was removed from the simulator for three days in the week leading up to the evaluation on the instructions of a Senior Manager so that certainly individuals could 'tune' with the pilot. The tiring then fouled up multiple QTG tests and was clearly wrong and the pilot was forced to sign a SoC that was clearly based on a lie. Another Senior Manager was also screamed at in a temper tantrum by said individual and also barred from the simulator. The Go/No Go decision comes along and then aforementioned Senior Manager and Senor Engineer then state to a cast of 30 —"we have to trust the decision of ti ]on Site". Needless to say, I tore straight into riland E.1117171about the lies and the unethicaticleceiffd nature of this comment as it meant I was set up to take the blame should it have gone wrong. It is a joke and nothing more — whilst 9 PMs were on Site last week during the evaluation, it was for a jolly/free meal. One PM even said that given that we are tiler budget, we should hire a yacht a sail around Miami harbour to celebrate and even asked submit the request...
I really hope we'll get to a dominant standard soon. But this subject is much more complex than I thought https://github.com/kubernetes/community/blob/master/contribu...
1. Dependencies in incompatible Merge Requests that need to be accounted for, see https://docs.gitlab.com/ee/user/project/merge_requests/merge... on how to do that.
2. Most merge requests can merge in previous changes changes, for that you can use merge trains as detailed in my other comment https://news.ycombinator.com/item?id=21679515
In GitLab we made merge trains https://docs.gitlab.com/ee/ci/merge_request_pipelines/pipeli... to solve this problem automatically.
With merge trains the merge requests with a passing feature branch is placed in a queue and tests are run against the combination of that branch and all the branches before it merged in. Since tests will pass 95%+ of the time the feature branches passes this can speed up the amount of merges you can get into master by 10x or more.