On Mon, Feb 10, 2014 at 1:43 AM, Dmitry Timoshkov dmitry@baikal.ru 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.
-- Dmitry.
What is the reasoning behind that, really? What is the point of having a version field that tells the developers absolutely nothing? As it stands the version field is only useful for a split second at report time to tell users "The version you're using is too old". This could be automated with a bit of javascript and prevent unnecessary reports.
J. Leclanche