Skip to content

Suggest guidelines around adding/rolling back new process

Michael Becker requested to merge wandering_person-main-patch-92f9 into main

Why is this change being made?

This adjustment aligns with the ongoing efforts to optimize the Engineering Workflow and maintain a high velocity.

This is a proposal to iterate on our approach to introducing new processes.

The goal is to establish a more balanced consideration between the cost of implementing a new process and the cost associated with its removal.

Currently, once a new process is added, there is no suggested guidance towards gauging its effectiveness or a suggested pathway to rollback the new process.

As part of our continuous iteration, this changes aims to add some guidance.

Historical Context

This MR was informed by the experience of trying to rollback a process which the GitLab Engineering Analytics team determined to be in-effective

Screenshots and Demo App

before after
image image

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 (slack post)
Edited by Michael Becker

Merge request reports