Skip to content

Indicate which items in the prioritization table are forced

Eric Brinkman requested to merge ebrinkman-master-patch-04778 into master

Why is this change being made?

We've made a change to the prioritization language to indicate they are guidelines. However, there are a few items in the table that have actual service level agreements/objectives PMs need to meet. This is a simple iteration to outline the two (Security and Availability) that are "forced."

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
  • Assign this change to the correct DRI
    • If the change relates to any part of the project other than updates to content and/or data files (e.g. team.yml) please make sure to ping @gl-static-site-editor in a comment for a review and merge.
    • If the DRI for the page/s being updated isn't immediate clear, then assign it to your manager.
    • 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

For help with failing pipelines reach out in #mr-buddies in Slack

Edited by Eric Brinkman

Merge request reports