On Feb 9, 2014, at 7:43 PM, Dmitry Timoshkov wrote:
Ken Thomases ken@codeweavers.com wrote:
I haven't been subscribed to the bug emails for long, but it seems there's an ongoing problem with users updating the Version field to the _newest_ affected version when we want it to indicate the _earliest_ affected version. Sorry if this is the sort of thing which has been discussed and dismissed before, but it seems the problem could be reduced by renaming the field.
Now they are going to think that they are supposed to set the version to Wine 1.0 or even 0.9, right? :)
Probably. :) There's a reason why I said "reduced" and not "eliminated" in the above. People will always be people.
In reality Wine version should be set to the one that user had used at the time it experianced the problem he/she were reporting. That's neither earliest nor the latest one, it's the one used at the bug reporting time.
The problem is that users retest with new releases of Wine and then update the Version field when they shouldn't. The desired behavior is for them to leave it at the earliest one where they found the problem. And if somebody happens to test an earlier version and finds that the bug existed back then, they should update the Version field to show that earlier version. Or, at least, that's what I've seen experienced bug wranglers do.
-Ken