Create new mailing list wine-isv?

Alexandre Julliard julliard at
Fri Dec 16 12:48:36 CST 2005

Tony Lambregts <tony.lambregts at> writes:

> Well that is a real sore spot with me. You know that I am a strong
> supporter of wine but it really concerns me that we have gone beta and
> not addressed preventing regessions from getting into our releases in
> any way. We currently have no freeze or notification of exactly when
> the next release is going to go out. Sure we had the one big code
> freeze just before 0.9 but then we went back to releasing without any
> notification. At his point even if our application maintainers test
> their app every day there is no way for them to prevent that
> regression going into the next release.

The idea is that people should test the releases. The point of the
beta phase is to encourage end users to test, and for this to happen
they need to be able to get binary packages, which is what the
releases are about. This is why I'm making releases more frequently
too, so that end users are able to test effectively without having to
build from CVS.

The goal is not to prevent regressions between every minor point
release, it's to make releases frequently enough that regressions can
be found and fixed quickly, so that they don't creep into the next
major release. Now, if you think that doesn't work I'm certainly open
to doing things differently. What do you suggest?

Alexandre Julliard
julliard at

More information about the wine-devel mailing list