I noticed Wine has a policy:
Why has my bug been marked as ABANDONED?
A bug report is marked as abandoned after a long period of inactivity. You will have been asked to update the current status of the bug, to test a workaround or to test in a new version of Wine but have not responded to the request. This inactivity leads to the logical conclusion that you have lost interest in resolving the issue and it has been abandoned.
You may choose to update the bug with the information requested. At this point you can reopen the bug if you wish to do so. Filing a new, duplicate bug serves no useful purpose.
The advantage ostensibly is to reduce the number of "open" bugs. However, the issue I see is:
OP posts a problem
Nobody responds to the bug report
After several years, somebody bumps the bug report with "Was this resolved with Version X?"
Obviously the OP hasn't received a response in years, they're either not going to care anymore or not see the bug report has been bumped
The bug report is marked as ABANDONED
Unless somebody has the exact same Wine version, specs, application and manages to reproduce the problem from whatever information is available in the OP, it's impossible to get the bug reopened. Yet, that's the policy.
I'm struggling to see what the advantage of this is. Does reducing the number of open bugs have any advantage? I noticed that huge applications like GCC don't have an abandoned bugs policy. Further, does the policy make sense?