This page describes the deployment and release approach used to deliver changes to users. The overall process consists of two significant parts:
The main priority of both deployments and releases is GitLab availability & security as an application running on both GitLab.com and for users running GitLab in their own infrastructure.
For testing purposes, all changes are deployed to GitLab.com before being considered for a self-managed release. Deployment and release cadences operate on different timelines with changes deploying to GitLab.com multiple times per day, and packages being released for self-managed users several times a month.
This overview shows how the two processes are connected:
The overall coordination and operation of the deployment and release process is the responsibility of the release managers.
See the GitLab Release Managers schedule to find out who the current release managers are.
You can contact the current Release Managers:
We use the
#f_upcoming_releases channels to discuss and coordinate deployments and releases. Automated deployment status announcements are made to the
If you need to escalate a request, please use the release management escalation process
Each week, the current Release Managers walk through the key Delivery Group metrics in the EMEA/AMER Delivery Weekly sync (YouTube Playlist). The goal is to share experiences about recent deployments and releases, and for the Group to identify ways we can improve our tools and processes.
|Release related tasks issue tracker||Link|
|Delivery team issue tracker||Link|
|Release manager schedule||Link|