“Gerrit would always have, essentially, just one single commit at a time that was being amended on each change. That worked great for dinosaurs like myself who like a pristine linear commit history where each commit pushed is fully functional. An equally valid option championed by those who cut their …

“Across the board, each upgrade caused 100 hours of developer downtime every month, That caused issues with our velocity. Of course, every time there was downtime, our deployments dropped.”

"GitLab takes the culture of the community and brings it to where you can actually codify how humans can interact together well. That’s difficult to capture, and I think GitLab does a really excellent job of not forcing people but really encouraging a collaborative beneficial work environment."

“The reality — before GitLab — was a lot of emails, a lot of other tools. It was a lot of really hard attempts at trying to get everybody on the same page,” Cardozo said. “But once we rolled out GitLab, we use it absolutely for everything.”

"With GitLab, we went from a completely isolated situation to a collaborative environment that enables better communication and coordination among diverse teams."

“That means we need to continuously adapt our software and our processing, and that means we need to be able to deliver faster and to deliver continuously. That's a revolution and that's where GitLab, of course, plays a key role for us.”

"GitLab increased the visibility of the information shared within the Agile development team. Project management combined with issue tracking on the code was very useful for us."

"GitLab's features allowed us to speed up our production cycle, which accelerated our development and deployment process."

"Cloud native GitLab efforts aligned well with our internal deployment processes."