Re: -current testing with VMware

["Dom De Vitto" <dom_(_at_)_DeVitto_(_dot_)_com>]

I think the general plan is that new releases should not break
anything that worked in the old release, assuming that the reason
it worked was not because the old code was crappy.

The bottom line if that if it doesn't work - and I'll test -current
ASAP myself, you can isolate why/what is bust, check the diffs
and fix/regress it yourself, any if it's little work I'd think
Theo would commit any fix.

Of course, now is the time to test it!

Dom
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Dom De Vitto                                       Tel. 07855 805 271
http://www.devitto.com                         mailto:dom_(_at_)_devitto_(_dot_)_com
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

 


-----Original Message-----
From: owner-misc_(_at_)_openbsd_(_dot_)_org [mailto:owner-misc_(_at_)_openbsd_(_dot_)_org] On Behalf
Of tony_(_at_)_libpcap_(_dot_)_net
Sent: Sunday, April 06, 2003 3:13 PM
To: misc_(_at_)_openbsd_(_dot_)_org
Subject: -current testing with VMware


What is the general consensus about testing -current with VMware? I
don't have any extra boxes laying around to test -current with, but my
main workstation is a powerhouse.

Are bugs found in VMware treated as if they were found in a "normal" PC
enviroment, or sort of put on the back burner until a few more similar
reports trickle down?

Thanks.

-- 
+ Cannot find nsabackdoor.dll. Please reinstall Windows.