Inside GitLab: How we release software patches

GitLab employs distinct approaches to manage software releases for its self-managed users and GitLab.com, focusing on timely updates and security. Self-managed users receive monthly updates on the 22nd, incorporating community-driven features and bug fixes, while GitLab.com benefits from a continuous delivery process called auto-deployments, which ensures rapid updates through automated pipelines. The GitLab Delivery team, responsible for both release types, strives to minimize manual intervention and reduce the mean time to production (MTTP) by automating processes and improving tool efficiency. The release manager plays a crucial role in assessing bug severity and determining the need for patch releases, especially for high-severity issues that significantly impact users. While self-managed releases require more manual actions, GitLab.com updates leverage CI/CD technologies for frequent and automated deployments. The Delivery team aims to enhance release velocity and streamline processes, with goals such as transitioning to a Kubernetes-based infrastructure and reducing MTTP from 50 hours to eight hours. GitLab encourages community contributions and feedback to further improve its delivery practices.

No tracked trend matches for this post yet.