Think of how we can improve the process around the "Merge requests requiring attention" triage package
Today, @toon brought up the fact the we seem to forget to handle the "Merge requests requiring attention" triage packages: https://gitlab.com/gitlab-org/gitlab-ce/issues?scope=all&utf8=✓&state=opened&label_name[]=triage-package&search=%22merge+requests+requiring+attention%22
There was a discussion with @gtsiolis @rpaik and @godfat about what we should do, how could we improve the situation.
A few things were suggested:
- "With 5 I might get around getting all 5 in the issue covered"
- "Maybe if they’re not responsive to our nudge in a month or so we disposition them somehow?"
- "Have a rotation to assign this weekly issue to, every x weeks one MR coach will get one assigned"
- "I would also consider having the gitlab-bot automatically closing the issue after a month or so as long as the merge requests get mentioned in a future relevant issue."
- "You could also pick 5 or 10 merge requests and leave the rest for another merge request coach. You shouldn’t feel that you have to triage all of them by yourself."
- "Ideally, I would:
- keep the smaller weekly issues as is (~20 items or less),
- close them automatically after a 2 weeks for example,
- create another package with a larger time scope (for example every 1 month) containing more merge requests or issues (for example 80 items or less), and
- close them after a 2 months for example."
Edited by Toon Claes