Wine 1.0 bugs, release criteria

[Dan Kegel]

At Wineconf 2007, I was appointed to be the guy who decides
(with Alexandre's approval) what bugs are 1.0 bugs and what aren't.
So I've started adjusting the "Target Release" fields on a few
bugs in Bugzilla.
Over the next month or so, I'd like Wine developers to nominate important
bugs for 1.0 by setting their "target release" field to 1.0.  Later on we'll
clean up and freeze the list somehow.

Also, I've put together a draft wiki page with our 1.0 release criteria; it's at
http://wiki.winehq.org/WineReleaseCriteria

Comments?
- Dan

[EA Durbin]

> Date: Sat, 6 Oct 2007 04:41:43 -0700> From: [e-mail]> To: [e-mail]> Subject: Wine 1.0 bugs, release criteria> > At Wineconf 2007, I was appointed to be the guy who decides> (with Alexandre's approval) what bugs are 1.0 bugs and what aren't.> So I've started adjusting the "Target Release" fields on a few> bugs in Bugzilla.> Over the next month or so, I'd like Wine developers to nominate important> bugs for 1.0 by setting their "target release" field to 1.0. Later on we'll> clean up and freeze the list somehow.> > Also, I've put together a draft wiki page with our 1.0 release criteria; it's at> http://wiki.winehq.org/WineReleaseCriteria%3E > Comments?> - Dan> >

I still have a whole slew of older applications(about 30-40 of them) that won't work because of just 3 bugs. 
http://bugs.winehq.org/show_bug.cgi?id=3743
http://bugs.winehq.org/show_bug.cgi?id=5948
http://bugs.winehq.org/show_bug.cgi?id=9030

And it would be nice to see the following MS Office bugs fixed by wine 1.0
http://bugs.winehq.org/show_bug.cgi?id=5163
http://bugs.winehq.org/show_bug.cgi?id=9023
_________________________________________________________________
Climb to the top of the charts!  Play Star Shuffle:  the word scramble challenge with star power.
http://club.live.com/star_shuffle.aspx?icid=starshuffle_wlmailtextlink_oct

[Dan Kegel]

On 10/6/07, EA Durbin  wrote:
> > http://wiki.winehq.org/WineReleaseCriteria
>
> I still have a whole slew of older applications(about 30-40 of them) that
> won't work because of just 3 bugs.
>  http://bugs.winehq.org/show_bug.cgi?id=3743
>  http://bugs.winehq.org/show_bug.cgi?id=5948
>  http://bugs.winehq.org/show_bug.cgi?id=9030
>
> And it would be nice to see the following MS Office bugs fixed by wine 1.0
>  http://bugs.winehq.org/show_bug.cgi?id=5163
>  http://bugs.winehq.org/show_bug.cgi?id=9023

Go ahead and set their "target release" field to 1.0.
(We might later defer them to a later release, but
that's ok.)
- Dan

[Louis Lenders]

Dan Kegel <dank <at> kegel.com> writes:
> At Wineconf 2007, I was appointed to be the guy who decides
> (with Alexandre's approval) what bugs are 1.0 bugs and what aren't.
> So I've started adjusting the "Target Release" fields on a few
> bugs in Bugzilla.
> Over the next month or so, I'd like Wine developers to nominate important
> Comments?
> - Dan

Maybe it's an idea to say "if a bug includes at least 5 duplicates (so 5 apps
suffering from the same bug) it can be automatically boosted to the 1.0 target
release". I was especially thinking of bug #7380.
( http://bugs.winehq.org/show_bug.cgi?id=7380 )
Couls i set this one on the list?
Any comments

[Dan Kegel]

Louis Lenders wrote:
> Maybe it's an idea to say "if a bug includes at least 5 duplicates
> (so 5 apps suffering from the same bug) it can be automatically
> boosted to the 1.0 target release". I was especially thinking of bug #7380.
> ( http://bugs.winehq.org/show_bug.cgi?id=7380 )

That's not a bad idea.  I've boosted that bug to 1.0.
- Dan

[Klaus Layer]

On Saturday 06 October 2007 13:41:43 Dan Kegel wrote:
> At Wineconf 2007, I was appointed to be the guy who decides
> (with Alexandre's approval) what bugs are 1.0 bugs and what aren't.
> So I've started adjusting the "Target Release" fields on a few
> bugs in Bugzilla.
> Over the next month or so, I'd like Wine developers to nominate important
> bugs for 1.0 by setting their "target release" field to 1.0.  Later on we'll
> clean up and freeze the list somehow.
>
> Also, I've put together a draft wiki page with our 1.0 release criteria;

it's at
> http://wiki.winehq.org/WineReleaseCriteria
>
> Comments?
> - Dan

Hi Dan,

can you please consider http://bugs.winehq.org/show_bug.cgi?id=9484 for 1.0.

Thanks,

Klaus

[Evil Jay]

http://bugs.winehq.org/show_bug.cgi?id=6155 also holds up quite a few
apps (some listed at http://wiki.winehq.org/IoCompletionPorts).  Fixing
it would make Wine feel a lot more 1.0ish to me.

-J,

Klaus Layer wrote:
> On Saturday 06 October 2007 13:41:43 Dan Kegel wrote:
> > At Wineconf 2007, I was appointed to be the guy who decides
> > (with Alexandre's approval) what bugs are 1.0 bugs and what aren't.
> > So I've started adjusting the "Target Release" fields on a few
> > bugs in Bugzilla.
> > Over the next month or so, I'd like Wine developers to nominate important
> > bugs for 1.0 by setting their "target release" field to 1.0.  Later on we'll
> > clean up and freeze the list somehow.
> >
> > Also, I've put together a draft wiki page with our 1.0 release criteria;
>
> it's at
> > http://wiki.winehq.org/WineReleaseCriteria
> >
> > Comments?
> > - Dan
>
> Hi Dan,
>
> can you please consider http://bugs.winehq.org/show_bug.cgi?id=9484 for 1.0.
>
> Thanks,
>
> Klaus

[Jesse Allen]

On 10/6/07, Dan Kegel  wrote:
> At Wineconf 2007, I was appointed to be the guy who decides
> (with Alexandre's approval) what bugs are 1.0 bugs and what aren't.
> So I've started adjusting the "Target Release" fields on a few
> bugs in Bugzilla.
> Over the next month or so, I'd like Wine developers to nominate important
> bugs for 1.0 by setting their "target release" field to 1.0.  Later on we'll
> clean up and freeze the list somehow.
>
> Also, I've put together a draft wiki page with our 1.0 release criteria; it's at
> http://wiki.winehq.org/WineReleaseCriteria
>
> Comments?
> - Dan

Dan,

Can find get a timeline for the feature freeze and the 1.0 release?
Also are we going to have a stable branch and a development branch
post 1.0? That way I can know the window for merging the DIB engine.
It'll likely be post 1.0 because I'm too busy in school at the moment.
It doesn't need to be a 1.0 bug because it only affects performance
mainly.

Jesse

[Dan Kegel]

On 10/6/07, Jesse Allen  wrote:
> > http://wiki.winehq.org/WineReleaseCriteria
>
> Can find get a timeline for the feature freeze and the 1.0 release?

As the wiki page says, we hope to have a "final" list of bugs
by the end of the year.  There have been some murmurings about
trying to do the release by June, but they're just rumors.
> Also are we going to have a stable branch and a development branch
> post 1.0? That way I can know the window for merging the DIB engine.
> It'll likely be post 1.0 because I'm too busy in school at the moment.
> It doesn't need to be a 1.0 bug because it only affects performance
> mainly.

Yeah, I think post 1.0 is fine.  We can call it 1.1 for now.

[Martin Bosner]

On Saturday 06 October 2007 17:12:51 Dan Kegel wrote:
> On 10/6/07, Jesse Allen  wrote:
> > > http://wiki.winehq.org/WineReleaseCriteria
> >
> > Can find get a timeline for the feature freeze and the 1.0 release?
>
> As the wiki page says, we hope to have a "final" list of bugs
> by the end of the year.  There have been some murmurings about
> trying to do the release by June, but they're just rumors.
> > Also are we going to have a stable branch and a development branch
> > post 1.0? That way I can know the window for merging the DIB engine.
> > It'll likely be post 1.0 because I'm too busy in school at the moment.
> > It doesn't need to be a 1.0 bug because it only affects performance
> > mainly.
>
> Yeah, I think post 1.0 is fine.  We can call it 1.1 for now.

Little bit late but maybe the "vote for a bug" feature in bugzilla should not 
only be a indicator for what should be fixed for 1.0 but also be more 
advertised.

Martin Bosner

[Louis Lenders]

Ok, here one on my wish-list:

All apps that currently fail on wine due to shdocvw/mshtml disfunctionality.
Almost all of these apps start fine using ies4linux. I did quite a lot of
testing of   demo's, and many of them fail because of this (in most cases you
just end up with a white screen). Actually i figured out what exact dlls  make
them fail in wine, and run in ies4linux. I currently use the script below to 
work around this , and in most cases it works quite fine (native shlwapi and
urlmon are probably only needed for  dll-dependancy, jscript and msls31 are not
implemented by wine)

(/sda3/native/ is where i've put my dlls from my windows-partition)
unalias cp
cp /sda3/native/shdocvw.dll ~/.wine/drive_c/windows/system32/
cp /sda3/native/shlwapi.dll ~/.wine/drive_c/windows/system32/
cp /sda3/native/urlmon.dll ~/.wine/drive_c/windows/system32/
cp /sda3/native/mshtml.dll ~/.wine/drive_c/windows/system32/
cp /sda3/native/mshtml.tlb ~/.wine/drive_c/windows/system32/
cp /sda3/native/jscript.dll ~/.wine/drive_c/windows/system32/
cp /sda3/native/MSLS31.DLL ~/.wine/drive_c/windows/system32/
cp /sda3/native/mlang.dll ~/.wine/drive_c/windows/system32/
regsvr32 jscript

(then run the app with native shdocvw, shlwapi,urlmon,mshtml,mlang).

[Dan Kegel]

Louis wrote:
> Ok, here one on my wish-list:
> All apps that currently fail on wine due to shdocvw/mshtml disfunctionality.

Hmm.   I looked at the 48 bugs in
http://bugs.winehq.org/buglist.cgi?product=Wine&component=wine-shdocvw
briefly, and marked a few of them that looked important as 1.0.  See
http://bugs.winehq.org/buglist.cgi?product=Wine&component=wine-shdocvw&a...
How's that for a start?

[Louis Lenders]

Dan Kegel <dank <at> kegel.com> writes:
> Louis wrote:
> > Ok, here one on my wish-list:
> > All apps that currently fail on wine due to shdocvw/mshtml disfunctionality.
>
> Hmm.   I looked at the 48 bugs in
> http://bugs.winehq.org/buglist.cgi?product=Wine&component=wine-shdocvw
> briefly, and marked a few of them that looked important as 1.0.  See

http://bugs.winehq.org/buglist.cgi?product=Wine&component=wine-shdocvw&a...
> How's that for a start?

That's very much ok, thanks.

[Stefan Dösinger]

Am Samstag, 6. Oktober 2007 13:41:43 schrieb Dan Kegel:
> Over the next month or so, I'd like Wine developers to nominate important
> bugs for 1.0 by setting their "target release" field to 1.0.  Later on
> we'll clean up and freeze the list somehow.

I think all the remaining DirectDraw rewrite regressions, as well as most 
other regressions in the d3d area. I do not have a complete list of them. 
I'll make one when I'm done with my exam, but if people could point out their 
unfixed d3d regression bugs it would make my life easier and make sure the 
bugs do not stay behind.(My bug assignment / CC list should find all of them 
though)