Project Hygiene: Triage Rotation Process

[rysweet]

Activity Begets Activity - Triage Process Documentation

To help ensure the health of the project and community the AutoGen committers have a weekly triage process to ensure that all issues and pull requests are reviewed and addressed in a timely manner. This discussion documents what to do when you are on triage duty.

Triage Daily Process

• Issues
  -- Review all new issues - these will be tagged with "needs-triage".
  -- Update the issue with the appropriate labels as needed.
  -- If you can resolve the issue or reply to the OP please do.
  -- If you cannot resolve the issue, assign it to the appropriate person.
  -- If awaiting a reply add the tag "awaiting-op-response".
  -- Review recently modified issues - in some cases an OP may have repled to us - remove the tag and reply as needed.
  -- Bonus: there is a backlog of old issues that need to be reviewed - if you have time, review these as well and close or refresh as many as you can.
• PRs
  -- The Ux on GH flags all recently updated PRs. Touch each one that is not in draft mode.
  -- If a PR is ready for review and you can provide one please go ahead. If you cant, please assign someone. You can quickly spin up a codespace with the PR to test it out.
  -- If a PR is needing a reply from the op, please tag it "awaiting-op-response".
  -- If a branch for the PR needs an update, please apply it if you can or tag the OP if its from a fork.
  -- If a PR is approved and passes CI, its ready to merge, please do so.
  -- If it looks like there is a possibly transient CI failure, re-run failed jobs.
• Discussions: look for recently updated discussions and reply as needed or find someone on the team to reply.
• Security: look through any securty alerts and file issues or dismiss as needed.