Wine is approaching the 0.9 release, and it's time to start fixing all the lingering bug reports in Wine's bug database. You can help the Wine developers do this even if you're not a developer yourself! All you have to do is spend an hour trying to reproduce a bug that somebody else filed. If you're interested, please go to http://kegel.com/wine/qa for step-by-step instructions. That page is new, and I'd appreciate feedback on any problems you run into while trying it. Once it's proved useful, I'll add it to the web pages at http://winehq.org. Thanks, and happy bug-hunting! Dan Kegel Occasional Wine contributor and QA cheerleader
Hi Dan, I'd be a very enthusiastic contributor to this if there was any chance that the things I worked on would be looked at by the developers. My negative input would be that I've filled out bug reports before and they've seemingly dropped into a black holw never to be addressed again. I have a couple that have been in there for a year or two! So, to be positive about the idea, which I like and support, how do we do work that ends up getting addressed? I can search the database for bugs I'd like to see fixed, then verify them if possible. That's cool, but it doesn't necessarily get my bugs addressed. All I'm saying is I don't want to spend an hour doing somethign that won't end up mattering. Thanks, Mark On 9/25/05, Dan Kegel <daniel.r.kegel@gmail.com> wrote:> Wine is approaching the 0.9 release, and > it's time to start fixing all the lingering > bug reports in Wine's bug database. > You can help the Wine developers do > this even if you're not a developer yourself! > All you have to do is spend an hour trying to > reproduce a bug that somebody else filed. > If you're interested, please go to > http://kegel.com/wine/qa > for step-by-step instructions. > > That page is new, and I'd appreciate feedback > on any problems you run into while trying it. > Once it's proved useful, I'll add it to the web pages > at http://winehq.org. > > Thanks, and happy bug-hunting! > > Dan Kegel > Occasional Wine contributor and QA cheerleader > > _______________________________________________ > wine-users mailing list > wine-users@winehq.org > http://www.winehq.org/mailman/listinfo/wine-users >
On 9/25/05, Dan Kegel <daniel.r.kegel@gmail.com> wrote:> Wine is approaching the 0.9 release, and > it's time to start fixing all the lingering > bug reports in Wine's bug database. > You can help the Wine developers do > this even if you're not a developer yourself! > All you have to do is spend an hour trying to > reproduce a bug that somebody else filed. > If you're interested, please go to > http://kegel.com/wine/qa > for step-by-step instructions. > > That page is new, and I'd appreciate feedback > on any problems you run into while trying it. > Once it's proved useful, I'll add it to the web pages > at http://winehq.org. > > Thanks, and happy bug-hunting! > > Dan Kegel > Occasional Wine contributor and QA cheerleader >Thanks to Robbert this bug: http://bugs.winehq.org/show_bug.cgi?id=2538 is verified with the latest snapshot. I can report that having followed Wine a bit through the Crossover Office product also I've seen this problem crop up with some other apps. I've thought for a long time this one would be a good one for the Devs. to look at. Unfortunately it is NOT and installation problem but a run time issue. Again, thanks to Robbert for trying it out. Cheers, Mark
Hi, I guess it's stating the obvious, but just using the standard Wine install I tried both Quicken 2005 and Office 2000 today. Neither installed. Is there any stated policy about things like Winetools? What should we expect Wine to handle and when should we resort to using things outside of Wine? Thanks, Mark On 9/25/05, Dan Kegel <daniel.r.kegel@gmail.com> wrote:> Wine is approaching the 0.9 release, and > it's time to start fixing all the lingering > bug reports in Wine's bug database. > You can help the Wine developers do > this even if you're not a developer yourself! > All you have to do is spend an hour trying to > reproduce a bug that somebody else filed. > If you're interested, please go to > http://kegel.com/wine/qa > for step-by-step instructions. > > That page is new, and I'd appreciate feedback > on any problems you run into while trying it. > Once it's proved useful, I'll add it to the web pages > at http://winehq.org. > > Thanks, and happy bug-hunting! > > Dan Kegel > Occasional Wine contributor and QA cheerleader > > _______________________________________________ > wine-users mailing list > wine-users@winehq.org > http://www.winehq.org/mailman/listinfo/wine-users >