In this case, though... It seems only 1 person has experienced this, and didn't care enough to even reply back. Closing it due to inactivity doesn't seem to be wrong, to me.
In this case, though... It seems only 1 person has experienced this, and didn't care enough to even reply back. Closing it due to inactivity doesn't seem to be wrong, to me.
If they never check it again, time is definitely better spent somewhere else.
And they should generally not be exported imho.
I totally agree about the "1 person" part, if several people report a problem it lends credibility to the problem. It may not even be a code bug, but may simply involve clarifying the documentation.
It's much better to leave them as "unconfirmed" or similar, so that other people can find them and add their own details or test cases. (Of course, I do assume that a project with a lot of "unconfirmed" bugs has no one even looking at the bug database, so it's a double-edged sword.)
The blog post linked to two other reports of the same issue (all closed or ignored), and the author mentioned that he himself had run into it prior to turning up these abandoned reports on their bug-tracker.
And really, given the egregiousness of the symbol exporting issue, it would be nearly impossible for only one person to have run into it.