logoalt Hacker News

PunchyHamstertoday at 12:38 AM0 repliesview on HN

I mean it can be useful to do that every year on old (say 2y+ tickets) but the way it is usually done is completely aisine

Sensible way would be probably something like this

* run cleaning yearly, on bugs say not touched (which is different than age!) for last 2 years * mark bug waiting for answer, add automated comment with "is it still happening/can you reproduce it on newest version?" * if that gets unanswered for say 3 months THEN close it.

that way at least it's "real" issue and even if solution is not being worked on maybe someone will see workaround that sometimes someone posts in the comment. Not create new one that gets closed for being duplicate...

Meanwhile I've seen shit as aisine as making bug stale 30 days after reporting.