GitLab Delivery
The GitLab Delivery Stage focuses on enhancing the reliability, efficiency, and speed of GitLab’s end-to-end software delivery across all platforms and offerings.
This is a draft page and it is currently a work in progress
Mission
The GitLab Delivery mission is to streamline and optimize the delivery, release, and deployment of GitLab across all platforms—SaaS, Self-Managed, and Dedicated. We aim to enhance the reliability, scalability, and efficiency of our processes, enabling customers to seamlessly adopt, deploy, and scale GitLab solutions. By evolving our tools, automation, and architectural practices, we are committed to delivering a consistent, secure, and high-quality experience that empowers both internal teams and customers to achieve more, faster.
The GitLab Delivery Stage Vision is defined in the Infrastructure Platforms direction pages
Vision and Direction
Our vision and direction are located with other product direction pages here.
Roadmap
Stage roadmap will be listed here
Top-level Responsibilities
GitLab Delivery stage is responsible for ensuring seamless, reliable, and efficient delivery of high-quality software. We focus on optimizing workflows, enabling collaboration, and driving continuous improvement to meet customer needs
Teams
The GitLab Delivery Stage is composed by the following teams:
TBD
On-call duties
- Release Manager ownership
- Build and Deploy Pipeline DRI
Project Management
GitLab Delivery Stage has an entry level Epic that collects all the groups roadmaps and projects in progress as a single view. This epic is also used for the weekly Grand Review
Issue Boards
Each working epic should be accompanied by an issue board. Issue boards should be tailored to the specific project needs, but at minimum it should contain the workflow labels shown on the workflow diagram.
GitLab Delivery AMA and Demo
Needs to be scheduled, starting in January 2026
History
Stage history will come here
Summary
Framework is a team within the GitLab Delivery Stage. This team takes ownership of the GitLab Environment Toolkit (GET) as instance lifecycle tool, Reference Architectures, tooling and frameworks related to upgrade path testing, and will ensure installation and upgrade paths are fully tested and reliable. We follow the same processes as listed on the GitLab Delivery Stage, unless otherwise stated on this page.
Mission
The Framework team intends to make GitLab easy to operate at any scale. GitLab is critical to our end users (developers) and a necessity for organizations most important business operations and workflows. The Framework team functions with autonomy to drive good quality within our Reference Architectures and GET above all else.
