Skip to content

Proposal for issue update process for Verify:Testing

Ricky Wiens requested to merge rw/testing-issue-updates into master

Overview

Please leave your feedback on this proposal. It is not set in stone. I'd appreciate a lot of discussion about this, particularly from the engineers who would be required to implement it.

Why is this change being made?

Right now it can be troublesome to figure out the status of issues that are in active development. Status updates can be spread across Merge Requests, the code, and slack, if they exist at all. This process would formalize an issue update process with a cadence of no less than weekly for issues that are in progress, making the issue itself the single source of truth for progress.

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.

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

Merge request reports