http://bugs.winehq.org/show_bug.cgi?id=35262
--- Comment #7 from Anastasius Focht focht@gmx.net --- Hello Rosanne,
--- quote --- However, if the bug is no longer present "because Wine evolved," then shouldn't the resolution be "Fixed"? "Invalid" implies this was never a bug in the first place. --- quote ---
Well, that's indeed debatable ;-)
From my point of view:
* bug reported against a Wine version from current development branch 1.7.x after it has already been fixed in newer version -> 'dupe' or 'fixed'
* bug reported against last official stable Wine 1.6.x after it has already been fixed in newer version from 1.7.x development branch -> 'dupe' or 'fixed'
* bug reported against Wine from stone age, <= 1.4.x or older development branch <= 1.5.x, 1.3.x -> 'invalid'
Yes, there were rare exceptions like the infamous Steam bug 35030 which broke _all_ versions older than Wine 1.7.8 Even Wine 1.4 and 1.5 versions got resolved as 'dupe' in that case.
In general the idea is to provide support for the last stable branch and the current development branch. Treating reports against ancient versions as 'invalid' is a way to indicate this. But yes, it might be a matter of personal preference.
Regards