Hi everyone, While triaging tickets for Google Summer of Code I went through dozens of invalid and stale tickets on JIRA that were still open. In addition to other issues, this makes it harder for new contributors to identify valid tickets to work on. Ideally any ticket that was triaged by a contributor should be good to work on, but this is not the current state of our JIRA.
I was wondering if we should adopt some strategy to auto-close JIRA tickets and/or GitHub PRs after a period of inactivity and wanted to bring this discussion to the community. One downside of this is that valid tickets might be auto-closed, but we could use a few strategies to mitigate that: a) use a long enough period (ie. 2 years), if an issue wasn't worked on within this period then it's probably not relevant enough and can be abandoned. This would already get rid of a large backlog of abandoned tickets dating back to as early as 2014 (or even earlier). b) if the issue hasn't been worked on for a large period but the community still finds it relevant, add some tag to prevent that ticket from being auto-closed. I think that this is something that is pretty easy to fix and will make our ticket tracking more reliable and easier for new contributors to get started, especially in the post 4.0 world. Please let me know what do you think, Paulo
