[Wine] Re: Understanding Wine's build processes/development cycle

[DanKegel]

Wine is a generic implementation of win32 (and win16 and win64),
it's not app-specific.

Working apps are tracked at http://appdb.winehq.org (see the
AppDB tab in the forum interface).

Adding support for an app means fixing the bugs it exposes in Wine.

Bug reports are tracked at http://bugs.winehq.org (see the Bugzilla
tab in the forum interface).

The best way to help the wine developers is to file clean bug
reports; if it's a regression, figuring out which commit broke the
app, and including that info in the bug report, improves 
the chances it'll get fixed.  (See 
http://wiki.winehq.org/RegressionTesting )

Some bugs are easy to fix, e.g.
http://bugs.winehq.org/show_bug.cgi?id=27339 was fixed in two
days (because it was small, and had an excellent bug report);
others are devilishly hard and take months or years.