http://bugs.winehq.org/show_bug.cgi?id=17831
--- Comment #6 from Austin English austinenglish@gmail.com 2009-03-27 15:47:57 --- (In reply to comment #5)
Regarding comment #3:
There should be an information before posting the bug that if the program isn't in English user should provide few steps on where to click to reproduce the bug
Yes, that probably should be done. Bugzilla's source is here: http://source.winehq.org/git/bugzilla.git/?a=shortlog
if you'd like to make a patch.
And I think that proposal made by CN Gnome is right. WINE shouldn't keep old bugs forever. There should be a warning email sent to reporter that the bug is going to be closed unless he will confirm it with the newest WINE release. If the developer won't update it in 2 weeks, bug should be closed as INVALID.
We don't already. But closing a bug just because it's old doesn't make sense. Some bugs we know aren't fixed, and are perfectly valid to keep open (implementing directplay, iPod support, etc.). Bugs with downloads can be tested by anyone. Bugs with no downloads, after not being active for 6 months are closed (albeit not automatically, I've got a pulse). I fail to see a real problem here...can you please explain what's wrong with the current system?