http://bugs.winehq.org/show_bug.cgi?id=22522
--- Comment #9 from Jörg Höhle hoehle@users.sourceforge.net 2010-04-30 02:51:30 ---
So the version field should either be the latest dev version or oldest known bad.
That makes sense to me. Somebody authorized please change Bugzilla to explain this in the bug submission page.
In the present case, my installation notes say that 0.9.28 was what I used initially (sorry for not reporting this bug earlier) and the bug is still present in current Wine. It does not imply a regression against 0.9.27.
There have been numerous times you've asked reporters not to change the original reported wine version.
Austin, I always felt the "Removing deprecated CVS/GIT version tag." message to be inconsistent with the other handling of versions in bugzilla. The rest of the message (asking to set version to earliest broken version) is fine. If the bug mentioned a regression, one should never change it, even if it's as old as 0.9.33 (e.g. bug #19773). If no regression was ever discovered, why change the version number, esp. as users get flamed when doing so without this invitation?