Delivery Team

1. You are here:
2. Handbook
3. Engineering
4. Infrastructure
5. Team
6. Delivery Team

On this page

• On this page
• Common Links
• Top-level Responsibilties
• Mission
• Vision
  • Short-term
  • Mid-term
  • Long-term
• Team
  • Team Members
    • Stable Counterparts
• Team training

Common Links

Workflow	How may we be of service?	GitLab.com Status	STATUS
Issue Trackers	Infrastructure: Milestones, OnCall	Production: Incidents, Changes, Deltas	Delivery
Slack Channels	#sre-lounge, #database	#alerts, #production	#g_delivery
Operations	Runbooks (please contribute!)	On-call: Handover Document, Reports

Top-level Responsibilties

• Acting as Release Managers for our monthly .com release process
• Migrate the company to a continuous delivery model (through automation)

Mission

The Delivery Team enables GitLab Engineering to deliver features in a safe, scalable and efficient fashion to both GitLab.com and self-managed customers. The team ensures that GitLab's monthly, security, and patch releases are deployed to GitLab.com and publicly released in a timely fashion.

Vision

By its own nature, the Delivery team is a backstage, non-user feature facing team whose product and output has a direct impact on Infrastructure's primary goals of availability, reliability, performance, and scalability of all of GitLab's user-facing services as well as self-managed customers. The team creates the workflows, frameworks, architecture and automation for Engineering teams to see their work reach production effectively and efficiently.

The Delivery team is focused on our CI/CD blueprint by driving the necessary changes in our software development processes and workflows, as well as infrastructure changes, to embrace the benefits of CI/CD.

Short-term

• Automate release generation, removing most of manual work
• Automate deployment process, managing and limiting impact on production
• Simplify security releases
• Streamline the process of limiting feature impact in production environments
• Enable feature testing at production-environment scale
• Create detailed architecture blueprints and design for CD on GitLab.com
• Develop and track KPIs to measure the team's impact on GitLab product delivery

Mid-term

• Drive the implementation of infrastructure changes to prepare GitLab.com for CD
• Eliminate the need for feature-freeze blackouts during the development cycle
• Shorten build times to allow for faster release times

Long-term

• Drive necessary changes that will lead to Kuberentes-based infrastructure on GitLab.com
• Fully automated releases for self-managed users

Team

Each member of the Delivery team is part of this vision:

• Each team member is able to work on all team projects
• The team is able to reach a conclusion independently all the time, consensus most of the time
• Career development paths are clear
• Team creates a database of knowledge through documentation, training sessions and outreach

Team Members

The following people are members of the Delivery Team:

Person	Role
Marin Jankovski	Engineering Manager, Delivery
Robert Speicher	Senior Backend Engineer, Delivery
Yorick Peterse	Staff Backend Engineer, Delivery
John 'Jarv' Jarvis	Senior Site Reliability Engineer, Delivery
Alessio Caiazza	Senior Backend Engineer, Infrastructure
John T Skarbek	Senior Site Reliability Engineer, Delivery

Stable Counterparts

The following members of other functional teams are our stable counterparts:

Person	Role
Filipa Lacerda	Senior Frontend Engineer, Release (CD), Verify (CI) & Delivery

Team training

Every Delivery team member is responsible for creating a training session for the rest of the team. See the page on team training for details.