Discussion: Agree on terminology for current and self-serve deployments
Problem statement
During recent Delivery:Orchestration discussions about how components and auto-deploys currently work we realized that many of our terms are vague or overloaded. This issue is intended to form a set of agreed terms for us to use when talking about the steps involved with deployments and releases.
For more context on the processes we're referring to on this naming issue please see &773 (closed) and the Delivery:Orchestration demo on the same topic.
Terminology
The terms proposed on this issue should be suitable for both today's processes and the future where we expect Stage groups to be able to select either Delivery-managed auto-deploy and releases processes or Stage-group owned processes.
Current name | Original term | Description |
---|---|---|
Centralized component versioning | SSOT gitlab-org/gitlab | A single-source-of-truth for the "current" component version on GitLab.com and in releases |
Managed auto-deploy | Automated Rollout | The Delivery group will automatically perform the rollout of merged changes via the “auto-deploy” pipeline |
Managed versioning | Automated Releases | The delivery group will create and manage all the branches and tags in a component's repository. With Managed Versioning, new branches, tags, and inclusion in the self-managed releases will be managed by the Delivery group and versioning aligned with the GitLab product versioning scheme detailed here |
Automated version updates | Automated update | Allowing version files to be automatically updated for Centralized component versioning. With this capability, a successful merge will cause versions to be updated and allow changes to be automatically included in Managed auto-deploys |
Independent deploy | Self-serve deploy | Providing a fully-independent deployment process to allow a team to deploy only their changes through to Production. Independent deploy pipelines will be designed in collaboration with the Delivery group to guarantee reliability. More details in readiness!120 (merged) |
Edited by Amy Phillips