https://bugs.winehq.org/show_bug.cgi?id=40834
--- Comment #10 from winetest@luukku.com --- (In reply to Rosanne DiMesio from comment #9)
Setting version field back to the original reported version. That field should not be changed; when updating, simply leave a comment that the problem is still present in the newer version.
You still need to retest in 1.9.21 or later and if the problem is still present, attach the full terminal output.
I think the version field should be updated in a case that the report is opened against really outdated wine and the next test is done with more recent. He just used too old wine at report time and the bug isnt an old one.
Bugs should be opened against wine-development version. Because wine offers also 1.8 stable it makes things a bit more complicated. 1.8 series of stable might have bugs that are already fixed at 1.9 series. And reporting against 1.8 would still be valid.
If people would really test against development version of wine this would prevent lots of bugs to be created that are already fixed.
Always reporting against development version would make the fixes eventually land in next stable and also the regressions would have been already fixed in development version and not in stable. If people would be active.