wine 1.8 schedule

Scott Ritchie scottritchie at
Wed Feb 11 16:04:09 CST 2015

On Wed, Feb 11, 2015 at 1:56 PM, Rosanne DiMesio <dimesio at>

> On Wed, 11 Feb 2015 21:18:46 +0100 (CET)
> Francois Gouget <fgouget at> wrote:
> > Users care that the application they are using does not stop working and
> > that's what can happen with the development branch.
> >
> That happens in the stable branch, too: when a new major stable release
> comes out, everything in the development branch goes into it, including
> unfixed regressions and bugs introduced by new features. The promise of
> "safe bugfixes only" only applies to minor releases in the stable branch,
> and most inexperienced users don't realize that.

To be clear, the whole concept of the "release process" is to generally
switch our focus to removing all known regressions and to be even more
conservative about introducing code that might cause regressions.  By way
of comparison, there were only 1 or 2 user-visible regressions going from
1.0 to 1.2, whereas there were something on the order of several hundred at
some point between 1.0 and each of the 1.1.x releases.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the wine-devel mailing list