Skip to content

Reorganize SLOs for easier consumption and allow overwriting generic ones with priority labels

Viktor Nagy (GitLab) requested to merge nagyv-slo-decision-tree-and-priorities 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.

We had a discussion on prioritization and SLOs at a Product meeting call (related notes here and here that pointed out that

  • issues with SLOs require a project management approach,
  • PMs regularly change the severity labels against the meaning of the severity when the impact does not match the label, and it would not be wise to prioritize an issue based on its appropriate severity,
  • it's getting hard to navigate our SLO decision tree.

This MR re-organizes the SLO sections.

  • It adds a new SLO table to disambiguate between the 3 existing SLO tables across the handbook
  • Fixes the header of the UX sections by moving it out from under Availability under the new Generic SLO section
  • Clarifies when and how priorities can overrule the SLOs set by severity labels.

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

Merge request reports