Inside GitLab: How we release software patches

What this post added

This post details the process of creating patch releases for self-managed GitLab customers and the auto-deployment process for GitLab.com. It explains the role of release managers, the severity-based criteria for patch releases, and the use of ChatOps and CI/CD for automating release tasks. For GitLab.com, it describes the use of scheduled pipelines for hourly checks, automated packaging, deployment, and QA testing, with a manual trigger for production deployment. The post also outlines future goals for the Delivery team, including reducing manual intervention, increasing release velocity, and migrating GitLab.com to Kubernetes infrastructure.