Document process for handling old or dormant issues in Static Analysis

Why is this change being made?

The demand for Static Analysis's time and attention outstrips our ability to satisfy it. We have adopted the MoSCoW Method as the means by which we scrutinize old or dormant issues in our backlog. This MR documents the problem we're trying to solve and the process we have adopted to address it.

Related issues

• gitlab-org/secure/general#179 (closed)

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
  • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added.
• Assign reviewers for this change to the correct DRI(s)
  • 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 in 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.
• If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR.
  • If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.

---