Skip to content

Proposed Dedicated for Government PCL dates for Q4-2025

Matt Kirkevoldrequested to merge
mckgl-main-patch-6a08 into main

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.

Please add the details saying why, not just what in this section. Example: We have discussed the topic in Slack - (copy of Slack conversation). The current process is not efficient, this MR makes the description of X more clear, and helps move Y forward.

As per instructions https://handbook.gitlab.com/handbook/engineering/infrastructure-platforms/gitlab-dedicated/#production-change-lock-pcl this is the proposed PCL dates for Dedicated for Government, Q4-2025.

This change updates a schedule table for planned code lockdowns (PCLs) - periods when code changes are restricted. The update removes an old holiday lockdown from December 2024-January 2025 and adds a new "Platform" column to specify which system the lockdown applies to. It then adds two new lockdown periods specifically for "Dedicated for Gov" platform: one for USA Thanksgiving week (late November 2025) and another for the year-end holidays (late December 2025 through early January 2026). Both lockdowns are marked as "Hard" restrictions due to low team availability during these holiday periods.

https://gitlab.com/gitlab-com/gl-infra/gitlab-dedicated/team/-/issues/10230+

https://gitlab.com/gitlab-com/gl-infra/gitlab-dedicated/team/-/issues/10229+

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
    • The when to get approval handbook section explains when DRI approval is required
    • The who can approve handbook section explains how to identify the DRI
    • If the MR does not require DRI approval, consider asking someone on your team, such as your manager.
    • The approver may merge the MR. If they approve but don't merge, you can merge.
  • 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
    • Division: If the update affects your division, share the MR in your division 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

Commits

  • proposed GDG PCL 2025

Merge request reports