Hello,
According to [1] the criteria for Wine 1.8 is the CSMT patch set. At FOSDEM 2015 Stefan Doesinger said at one moment something like CSMT is not ready yet(I don't remember exactly how he formulated it as he wasn't talking specifically about CSMT).
Wine 1.6 was released in July 2013 [2] so more than 18 months ago. And 1.6 took 15 months to be released.
A lot of good work has been put into 1.7 branch
git rev-list wine-1.6..wine-1.7.35 | wc -l
7708
Currently still a lot of people are using the 1.6 branch. So on the forum Roseanne often has to ask people to upgrade from the stable branch to the development one. On bugzilla, the triagers very often have to close bugs reported on 1.6 and already close in 1.7 (latest example a few hours ago [3])
I do not deny that the work to release is negligible (for example I see that in bugzilla there are 71 bugs tags as regressions [4] for 1.7).
Maybe not having the CSMT patch set would also not be the best PR possible. But the number of commits and bugs solved is clearly good PR and good for the users.
I'm not asking for an immediate release for sure, but to start a discussion on: - maybe a change of criteria for wine-1.8 - a rough schedule for wine-1.8
in order to give most of Wine users the best of what is being produced by you guys.
Cheers, Marc
[1] http://wiki.winehq.org/WineReleaseCriteria [2] https://www.winehq.org/news/2013071801 [3] https://bugs.winehq.org/show_bug.cgi?id=38023 [4] https://bugs.winehq.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NE...