Skip to content

Guidance for handling dormant reviews

Thomas Woodham requested to merge 1014-tw-secure-dormant-reviews into master

Why is this change being made?

One of the main items which came up in the Secure sub-department's 13.4 retrospective revolved around how long it can take to get feedback on merge requests. This MR adds guidances and potential strategies for navigating this scenario in Secure's section of the handbook.

The target for this change is in a part of the handbook which is yet to be promoted out of a draft state. Promoting this page out of a draft state will occur in a subsequent MR.

Related issues

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 DRI for the page/s being updated isn’t immediately 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.
    • If the changes relate to any part of the project other than updates to content and/or data files please make sure to ping @gl-static-site-editor in a comment for a review and merge. For example changes to .gitlab-ci.yml, JavaScript/CSS/Ruby code or the layout files.
Edited by Thomas Woodham

Merge request reports