Cleanup Stale Bugs across various engineering groups
Problem
There are a lot of stale bugs in the gitlab-org group This issue is to bring about bug hygiene and help the engineering teams by reducing the noise due to stale bugs.
What are stale bugs?
We could define stale bugs based on the severity of the impact that the bug causes and on the activities happening in the issue. Bugs that have had no human activity for the past 12 months could be considered stale bugs.
Proposal
Please note that the description contains the most recent update, after considering the feedback in the below discussions (Dated: 10-05-2020)
A weekly triage policy will be put in place, to take action on the ~S3/~S4 bugs that are stale with enough notification to the author of the bug.
- If a bug (an issue with a ~bug label) is inactive for atleast 12 months AND if it is not an ~S1 / ~S2 bug, it might be identified as eligible for auto-closure. At this point, vintage label is applied, which means this issue is older than a year.
- As a first step, inactive vintage bugs are labeled as stale bugs. The author of the issue is asked to check whether the reported bug still persists and is asked to comment accordingly within the next 7 days.
- After 7 days, one of the below mentioned actions happen:
At any point, open bugs with vintage label should give the list of all bugs (with no human update for at least a year) that are still valid and needs prioritisation.
This triage policy will affect all the projects in gitlab-org group
stale bug:
Conditions that qualify to be considered a- ~bug which meet the below criteria:
P.S: If needed any issue that was auto-closed can be reopened manually with corresponding comments for reopening, and it will not be considered for auto-closure again.