http://bugs.winehq.org/show_bug.cgi?id=21220
--- Comment #8 from Austin English austinenglish@gmail.com 2010-01-02 11:41:44 --- (In reply to comment #7)
(In reply to comment #6)
Cause it means nothing and requires commenting from time to time anyway.
It did mean suffix of the version string. And now it requires changing version field from time to time :(
Now if someone forgets such temporarily decremented version setting in a bug report, the report states false fact. I consider this as a bug.
It's not false. Version just indicates latest release before tested and simplifies version based querying.
In what way it does simplify? Lets assume another guy comes and sees version 1.1.35 in some regression report. Then he does regression hunt between v1.1.34 and v1.1.35. What does he find? Just that v1.1.35 is good AND bad.
It wouldn't call that simplification.
Often, regressions in git are fixed before a release is made. The solution is to put the current git commit in the bug comments somewhere. Yes, it's not perfect, but it's better than the previous solution where CVS/GIT could describe current git, or a release that is 6 years old.