Wine code freeze in seven weeks; volunteers needed to fix 1.0 bugs

[James McKenzie]

Dan Kegel wrote:
> Per http://wiki.winehq.org/WineReleasePlan,
> in early May, Wine's trunk will go into code freeze,
> and only small, obvious bugfixes will be accepted.
>
> Now might be a good time to start winding down
> development, and switching to cleaning up loose ends.
>
> http://bugs.winehq.org/buglist.cgi?query_format=advanced&product=Wine&target_milestone=1.0.0&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED
> lists 99 bugs targeted for the 1.0.0 release.
> When the code freeze starts, we will defer most of the
> remaining unfixed 1.0 bugs to the 1.1 release.
>
> A bunch of them have patches or good analysis
> attached, and it'd be a shame if those got deferred,
> so please have a look at these, and if you have time,
> pick an easy one to fix.
> - Dan
>
>
>   
Dan:

6254 had a proposed fix from Tony Rollo, and was worked on both Lai 
Zhang and myself.  Can I send the proposed patch to the dev list for 
review?  The patch fixes the problem stated.

James McKenzie