http://bugs.winehq.com/show_bug.cgi?id=740
*** shadow/740 Wed May 29 12:21:15 2002 --- shadow/740.tmp.28659 Wed May 29 13:55:48 2002 *************** *** 57,59 **** --- 57,97 ---- http://www.winehq.org/docs/wine-devel/cvs-regression.shtml It will be easier for you then for other users as you already use CVS. With patch in hand it is usually very easy to fix the issue. + + ------- Additional Comments From apa3a@yahoo.com 2002-05-29 13:55 ------- + David, please post your comments to the bug description, so they won't be lost + to developers who can start to work with the issue later. + + Copied from David's email: + ******************************************************************** + > + As I understand we can't have access to your database application + to test it, so + > + we need your help in researching the issue. + + You are correct & worse, access to the remote database requires one of + our IP numbers. + + > + Will it be difficult for you to find the patch which broke your + application? + > + See for details: + > + http://www.winehq.org/docs/wine-devel/cvs-regression.shtml + > + It will be easier for you then for other users as you already use + CVS. + > + With patch in hand it is usually very easy to fix the issue. + + I can try to do the regression hunt, but this looks like it will take + alot of time. I can probably give someone a guest account if that + would be faster? + ******************************************************************** + + I agree, the regression testing can take some time, but does not require high + qualification :-( Sorry, I don't think that anybody can make it much faster. + + If you have powerful machine it won't take long time to run rebuild cycle + "configure && make depend && make install". + If you have a month of untested patches you'll need 5 tests to find a day. Then + look at the patches in that day (http://cvs.winehq.com) and concentrate your + testing on suspicious ones - will probably take 2-4 additional runs. + + Guest account may help for developer to research the bug further (probably 5% + chance as soon as a patch is found). \ No newline at end of file