[Wine] Code freeze, or catching up with new features

[Austin English]

On Sun, May 11, 2008 at 6:05 PM, oiaohm <wineforum-user at winehq.org> wrote:
> Really I would love to see a code freeze every 6 months just to mop out out standing regressions.   So that once applications get to plat they stay that way.
>
>
>
>
>
>

I don't know if the topic has been discussed, but that's a good idea
for the 1.2 branch, 1.4, etc. Do a code freeze, make sure our
guaranteed apps haven't hit any regressions, clear out any standing
regressions in non-guaranteed apps, release, and set a new higher
target.