Skip to content

Production Change Lock - GitLab Dedicated - End of Year holiday 2023

Oriol Lluch requested to merge pcl-GitLab-Dedicated into master

Why is this change being made?

💡 Provide a detailed answer to the question on why this change is being proposed, in accordance with our value of Transparency.

To reduce risk when GitLab Team Member availability is substantially reduced, we are introducing a Production Change Lock (Hard) for the 2023 year-end holidays break on GitLab Dedicated Instances.

In this MR, we formalize the Production Change Lock for GitLab Dedicated which is a simplified version of the PCL for GitLab.com.

The PCL starts on the 22nd of December 2023, 23:00 UTC, and ends on the 6th of January 2024, 09:00 UTC.

For reference, the introduction of this PCL means that GitLab 16.7 will be rolled out to GitLab Dedicated instances during the maintenance windows starting on Jan 8th, 2024.

Related issue: https://gitlab.com/gitlab-com/gl-infra/gitlab-dedicated/team/-/issues/3486

To merge, approval is requested from:

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 Marin Jankovski

Merge request reports