Re: Wine 1.0 bugs, release criteria
On Saturday 06 October 2007 17:12:51 Dan Kegel wrote: > On 10/6/07, Jesse Allen <[EMAIL PROTECTED]> 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
Re: Wine 1.0 bugs, release criteria
On Tuesday 16 October 2007 20:35:26 Denali Coldstar wrote: > Dan Kegel 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 > *>* > *> > === > > Good Afternoon, > > I believe Ventrilo meets the criteria set forth in > http://wiki.winehq.org/WineReleaseCriteria. In the gaming community, when > you use VOIP applications, it generally boils down to TeamSpeak and > Ventrilo. While TeamSpeak has a Linux native client, Ventrilo doesn't. I > can't necessarily say Vent holds 50% of the market, but I feel safe in > saying it holds a significant share of it. This is mainly based on the > fact several companies have sprung up over the years to offer hosting of > Vent servers. The client can be freely downloaded from the Ventrilo > website ( http://www.ventrilo.com/download.php), but I'm not sure if it can > be grabbed with wget. Lastly, it does not have an autoupdate but it will > pop up a notice if a new version is available. > > If it is found that Ventrilo would be a suitable program for consideration > in the 1.0 release, the following issues would need to be addressed: > > http://bugs.winehq.org/show_bug.cgi?id=1348 > http://bugs.winehq.org/show_bug.cgi?id=5178 > http://bugs.winehq.org/show_bug.cgi?id=5924 > http://bugs.winehq.org/show_bug.cgi?id=5978 > > Thank you for reading this post. > > Steve Hello all, I would like to nominate bug #5828. It causes the system cursor to be displayed instead of the proper game cursors in games such as C&C Generals and C&C 3 Tiberium Wars, making them less eye-catchy and harder to play. There is a proposed patch (not suitable for inclusion according to the author) to make the cursors work, so advanced users won't be too harmed since they can compile a custom Wine to get the games working. But considering that C&C 3 is 3rd top rated in the AppDB and has a free demo, I'd say we should make it work out-of-the-box. http://bugs.winehq.org/show_bug.cgi?id=5828 Bug #8048 to support a shader setting higher than 'lowest' might also be worth considering. http://bugs.winehq.org/show_bug.cgi?id=8048 Alexander N. Sørnes
Wine 1.0 bugs, release criteria
Dan Kegel 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 *>* *> === Good Afternoon, I believe Ventrilo meets the criteria set forth in http://wiki.winehq.org/WineReleaseCriteria. In the gaming community, when you use VOIP applications, it generally boils down to TeamSpeak and Ventrilo. While TeamSpeak has a Linux native client, Ventrilo doesn't. I can't necessarily say Vent holds 50% of the market, but I feel safe in saying it holds a significant share of it. This is mainly based on the fact several companies have sprung up over the years to offer hosting of Vent servers. The client can be freely downloaded from the Ventrilo website ( http://www.ventrilo.com/download.php), but I'm not sure if it can be grabbed with wget. Lastly, it does not have an autoupdate but it will pop up a notice if a new version is available. If it is found that Ventrilo would be a suitable program for consideration in the 1.0 release, the following issues would need to be addressed: http://bugs.winehq.org/show_bug.cgi?id=1348 http://bugs.winehq.org/show_bug.cgi?id=5178 http://bugs.winehq.org/show_bug.cgi?id=5924 http://bugs.winehq.org/show_bug.cgi?id=5978 Thank you for reading this post. Steve
Re: Wine 1.0 bugs, release criteria
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) signature.asc Description: This is a digitally signed message part.
Re: Wine 1.0 bugs, release criteria
I would like to propose this one: http://bugs.winehq.org/show_bug.cgi?id=5351 2007/10/7, Karl Relton <[EMAIL PROTECTED]>: > > I would like consideration given to > > http://bugs.winehq.org/show_bug.cgi?id=3739 > http://bugs.winehq.org/show_bug.cgi?id=4362 > > I would imagine Adobe PhotoDeluxe might be quite common among home users > (who may get a copy with their digital camera, and not fork out for full > Photoshop). > > The other bug has a proposed fix - and something of a testcase to prove > it. Its just a matter of getting it squared up and applied. > > Regards > Karl > > > > -- Jaime Rave Torres GNU/Linux User - Ubuntu Feisty http://sobrelibertad.blogspot.com/
RE: Wine 1.0 bugs, release criteria
I would like consideration given to http://bugs.winehq.org/show_bug.cgi?id=3739 http://bugs.winehq.org/show_bug.cgi?id=4362 I would imagine Adobe PhotoDeluxe might be quite common among home users (who may get a copy with their digital camera, and not fork out for full Photoshop). The other bug has a proposed fix - and something of a testcase to prove it. Its just a matter of getting it squared up and applied. Regards Karl
Re: Wine 1.0 bugs, release criteria
Dan Kegel 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&target_milestone=1.0.0 > How's that for a start? > > That's very much ok, thanks.
Re: Wine 1.0 bugs, release criteria
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&target_milestone=1.0.0 How's that for a start?
Re: Wine 1.0 bugs, release criteria
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).
Re: Wine 1.0 bugs, release criteria
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 > > > > > > >
Re: Wine 1.0 bugs, release criteria
On 10/6/07, Jesse Allen <[EMAIL PROTECTED]> 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.
Re: Wine 1.0 bugs, release criteria
On 10/6/07, Dan Kegel <[EMAIL PROTECTED]> 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
Re: Wine 1.0 bugs, release criteria
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 -- Klaus Layer Walldorf, Germany GPG Fingerprint: 466D 12F8 28A3 D137 A77E FC3B 271C 2D79 6F5E 94C9 pgpjM2FyO0I34.pgp Description: PGP signature
Re: Wine 1.0 bugs, release criteria
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
Re: Wine 1.0 bugs, release criteria
Dan Kegel 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
Re: Wine 1.0 bugs, release criteria
On 10/6/07, EA Durbin <[EMAIL PROTECTED]> 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
RE: Wine 1.0 bugs, release criteria
> Date: Sat, 6 Oct 2007 04:41:43 -0700> From: [EMAIL PROTECTED]> To: > wine-devel@winehq.org> 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> > 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
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 Comments? - Dan
