Stale tickets/gerrit patches create unnecessary noise and confusion - particularly when the content relates to code or UI that no longer exists or has changed significantly. In many cases the owner/creator of the Gerrit/Phabricator ticket may have left the movement and are unlikely to ever act. Recently patches were raised on 5 year+ old tickets in one of my repos where patches were not welcomed wasting volunteer time.
- Allow certain phabricator/gerrit maintainers to opt out before the bulk job
- Define what a stale patchset/phab ticket is "e.g. has seen no activity in 2 years"
- Comment on open and stale phabricator tickets requesting that an edit is made to the description to ensure the ticket is valid. If this doesn't happen the task will be declined or the patch abandoned.
- Leave a grace period for action to be taken if necessary e.g. 1 month
- Abandon open and stales patchsets/tickets where no activity occurs with a message pointing to this ticket. Make it clear that they can be reopened if necessary.
Result: More relevant and actionable Phabricator tickets.