Some notes from wineconf about the 1.4 release -- are we on track?

[Scott Ritchie]

According to Alexandre...

1.4 will be out "sometime in 2011"

At the time of wineconf we already had several new features: animated
cursors, 64-bit Gecko, native cursor themes, AcceptEx support, mono packages

Goals for the 1.4 release:

Successful 64-bit make test
Successful 32-bit make test ;)
RTL support
Transparency/compositing
XInput2
USB support
Audio redesign
DIB Engine

There were also these suggestions:
Addons or plugins of some sort
 - eg a theme for GTK-grabbing
Dosbox integration
 - possibly using Windows versions as add-on
 - get rid of Winedos code

Plus, of course, the general goal of making more applications work :)

It seems like we're making serious progress.  Have any of these stalled
or become less important?  Has any new big feature not listed above been
done that's worth listing?  Is "sometime in 2011" still the best guess
for 1.4's release?

Thanks,
Scott Ritchie

[Louis Lenders]

Scott Ritchie <scott <at> open-vote.org> writes:
> According to Alexandre...
>
> 1.4 will be out "sometime in 2011"

.
.
.
> Plus, of course, the general goal of making more applications work :)
>
> It seems like we're making serious progress.  Have any of these stalled
> or become less important?  Has any new big feature not listed above been
> done that's worth listing?

If I may suggest another thing worth fixing: bug
http://bugs.winehq.org/show_bug.cgi?id=18640

This would allow a whole bunch of apps running in wine again. According to Hans'
comment here (http://bugs.winehq.org/show_bug.cgi?id=25060#c10) the .Net 3.5
should be able to finish fine as well in current git (haven't tested that yet
myself), so by fixing the aforementioned bug we could make a lot of WPF-apps in
.Net 3.0 and .Net 3.5 running in wine. ATM Mono is no go for these applications.

I also tested a few .Net 4.0 apps in wine recently and most of them also seem to
choke in the same bug. I'm not sure how difficult this bug is to fix, but the
d3d9 part seems rather easy to fix, not sure how hard the rest of the bug is to
solve.

Is "sometime in 2011" still the best guess
> for 1.4's release?
>
> Thanks,
> Scott Ritchie

[Henri Verbeet]

On 10 July 2011 11:27, Scott Ritchie  wrote:
> done that's worth listing?  Is "sometime in 2011" still the best guess
> for 1.4's release?

I'd guess late 2011 or maybe early 2012. I think the main criterion is
having a solid 400 regressions. It's currently at 399, but it
fluctuates a bit.