Skip to content

Rename CD section to Delivery section

Viktor Nagy (GitLab) requested to merge nagyv-delivery-section into master

Why is this change being made?

With the split of the Ops section into CI and CD sections, the CD section is ambiguous. Does it stand for continuous deployment or continuous delivery? Either option excludes the other as they don't share a set-subset relationship.

Moreover, the remaining groupenvironments owns the Delivery direction, and the scope of the section align with that of application delivery in general, including continuous deployment, continuous delivery, mobile, cloud-native, etc.

Expected name conflict

There is an internal-facing delivery group. The name clash caused issues in the past already, and we agreed to

  • keep the delivery group name as there is much automation relying on the labels
  • keep the delivery direction name as this serves best our users

As the Delivery section is in charge of the Delivery direction, this change likely serves our users best, at the same time, there are no plans to rename the delivery group as a result of this change.

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

  • Provided a concise title for this Merge Request (MR)
  • Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
    • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
  • Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
    • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
    • The when to get approval handbook section explains the workflow in more detail
  • For transparency, share this MR with the audience that will be impacted.
    • Team: For changes that affect your direct team, share in your group Slack channel
    • Department: If the update affects your department, share the MR in your department Slack channel
    • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR
Edited by Viktor Nagy (GitLab)

Merge request reports