Skip to content

Remove FCL due date

Sean McGivern requested to merge remove-fcl-due-date into master

Why is this change being made?

We had a conversation on Slack and agreed that this can continue as it is. Although we're removing a specific date to review this, the policy can be changed or removed at any time anyway.

We also have !99778 (merged) open to improve visibility for Product into FCLs in their areas, as this was a key item of feedback from that discussion.

FCL history

On 2022-09-08, we introduced (!89604 (merged)) a Feature Change Lock process (https://about.gitlab.com/handbook/engineering/#feature-change-locks). In !89799 (merged), we added a review after six months, which is now.

I put together this list of FCLs to date from the Reliability & Security Standup (https://docs.google.com/document/d/1vww0BfRzHtrGhMppTEw5Q27KSzD1e72dmJ3XoppxC-A/edit#) and Slack (looking for channels starting with 'fcl'). For some FCLs I could not find a specific FCL issue or epic, so I’ve linked the RCA or incident instead.

FCL start Stage Group Issue
2021-09-07 Create Gitaly gitlab-org/create-stage#12916 (closed)
2021-09-09 Release Release https://gitlab.com/gitlab-org/ci-cd/release-group/release/-/issues/83
2021-09-17 Verify Pipeline Insights https://gitlab.com/gitlab-org/ci-cd/pipeline-insights-group/-/issues/74
2021-09-23 Enablement Distribution gitlab-org/distribution&17 (closed)
2021-11-10 Growth Product Intelligence gitlab-org/gitlab#345417 (closed) (RCA)
2021-11-17 Enablement Sharding https://gitlab.com/gitlab-org/sharding-group/group-tasks/-/issues/8
2021-12-01 Verify Pipeline Insights https://gitlab.com/gitlab-org/ci-cd/pipeline-insights-group/-/issues/82
2021-12-15 Plan Product Planning https://gitlab.com/gitlab-org/plan/-/issues/492
2022-02-09 Manage Optimize gitlab-org&7529 (closed)
2022-02-17 Growth Activation https://gitlab.com/gitlab-org/gitlab/-/issues/353188 (RCA)
2022-02-22 Enablement Global Search https://gitlab.com/gitlab-org/search-team/team-tasks/-/issues/87

Author Checklist

  • Provided a concise title for the 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.
  • Assign reviewers for this change to the correct DRI(s)
    • 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 in 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.
Edited by Sean McGivern

Merge request reports