GitLab-CE Stale Issue Closure Proposal
In an attempt to gain some control of the ~4700 issues in the GitLab-CE project, we plan to perform a closure of "Stale Issues". The number of new issues raised per day is rising and the rate of issues opened is currently outweighing the rate of closures.
Stale Issues are issues that are:
- Open
- Have not been updated in the past 4 months
- Uncategorised
- No labels
- No milestones
- No assignee
The number of Stale Issues as of 29th August 2016 is 690 and they can be viewed in this Google Sheet (using the "Stale Issues" filter view):
The closure of each issue will inform the author and they will be free to reopen the issue if the feature proposal is still relevant, or the bug still reproducible.
The process will go as follows:
- Use the API to close the issues classified as "Stale"
- The issues will be closed with the following message:
Hi @author_username,
First of all, thank you for raising an issue to help improve the GitLab product. We're sorry about this, but this particular issue has gone unnoticed for quite some time. To establish order in the GitLab-CE Issue Tracker, we must ensure that every issue is correctly labelled and triaged, to get the proper attention.
This issue will be closed, as it meets the following criteria:
- No activity in the past 4 months
- Unlabelled
- Unassigned
- It's not associated with a particular milestone
We'd like to ask you to help us out and determine whether this issue should be reopened.
If this issue is reporting a bug, please can you attempt to reproduce on the latest version of GitLab or GitLab.com, to help us to understand whether the bug still needs our attention.
If this issue is proposing a new feature, please can you verify whether the feature proposal is still relevant.
Thanks for your help
- I'll subscribe to each of the 690 issues before closing
- I'll receive a notification for each issue that is reopened or commented on
Each issue author will receive a notification or email, so I apologise for the torrent that some may receive. There are still more untriaged issues but they are not quite old enough to be classified as stale, just yet.
Please can you voice any concerns or suggestions regarding this approach here.