Wine code freeze in seven weeks; volunteers needed to fix 1.0 bugs
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... 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 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... 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
<jjmckenzie51(a)sprintpcs.com> wrote:
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.
Lei, feel like resubmitting http://winehq.org/pipermail/wine-patches/2007-June/040182.html ? - Dan
On Sat, Mar 15, 2008 at 6:06 PM, Dan Kegel <dank(a)kegel.com> wrote:
<jjmckenzie51(a)sprintpcs.com> wrote:
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.
Lei, feel like resubmitting http://winehq.org/pipermail/wine-patches/2007-June/040182.html ? - Dan
That patch is old and crusty and doesn't apply anymore. James should have an updated version.
Lei Zhang wrote:
On Sat, Mar 15, 2008 at 6:06 PM, Dan Kegel <dank(a)kegel.com> wrote:
<jjmckenzie51(a)sprintpcs.com> wrote:
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.
Lei, feel like resubmitting http://winehq.org/pipermail/wine-patches/2007-June/040182.html ? - Dan
That patch is old and crusty and doesn't apply anymore. James should have an updated version.
Lei: I do and I will look at it this afternoon. It is supposed to be very rainy with thunderstorms here in Southern Arizona (we'll take every drop of rain we can get, we are in a drought) so I should be able to look at it and see if it applies to .57. If it does, I will send it first to this list for comments and then after fixing what I can, to patches for integration. I would like to publically thank Tony Rollo and you for the work you did, the both of you did the heavy work, I'm just cleaning it up. James McKenzie
On Mar 16, 2008, at 7:13 AM, James McKenzie <jjmckenzie51(a)sprintpcs.com> wrote:
Lei Zhang wrote:
On Sat, Mar 15, 2008 at 6:06 PM, Dan Kegel <dank(a)kegel.com> wrote:
<jjmckenzie51(a)sprintpcs.com> wrote:
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.
Lei, feel like resubmitting http://winehq.org/pipermail/wine-patches/2007-June/040182.html ? - Dan
That patch is old and crusty and doesn't apply anymore. James should have an updated version.
Lei:
I do and I will look at it this afternoon. It is supposed to be very rainy with thunderstorms here in Southern Arizona (we'll take every drop of rain we can get, we are in a drought) so I should be able to look at it and see if it applies to .57. If it does, I will send it first to this list for comments and then after fixing what I can, to patches for integration.
I would like to publically thank Tony Rollo and you for the work you did, the both of you did the heavy work, I'm just cleaning it up.
James McKenzie
How crazy! I'm just now driving through that rain on my way to LA :) James
Hi,
That patch is old and crusty and doesn't apply anymore. James should have an updated version.
One thing I can add from looking at that patch is that the comments about the deficiency of MS richedit tables handling are true only for versions <=2.0. Later versions, including msftedit, improved tables handling with each new version. -- Ph
On Sunday 16 March 2008 00:15:06 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.
Could we please come up with a good plan on how to handle Summer of Code contributions _before_ we do a code freeze? I remember that the 2005 code freeze just when I was starting to get my patches in was immensely frustrating. Git will make this easier, but we _need_ to decide how we want to handle ongoing contributions. I know the idea of a code freeze is to get people working on existing bugs but for the SoC students that's just not an option. If we don't integrate the code during SoC, I doubt we're really going to use it. I still remember the ClamAV plugin that never made it to the master branch. Cheers, Kai -- Kai Blin WorldForge developer http://www.worldforge.org/ Wine developer http://wiki.winehq.org/KaiBlin Samba team member http://www.samba.org/samba/team/ -- Will code for cotton.
participants (6)
-
Dan Kegel -
James Hawkins -
James McKenzie -
Kai Blin -
Lei Zhang -
Phil Krylov