Date: Tue, 25 Mar 1997 18:16:02 +1000 (EST) From: Stephen McKay <syssgm@dtir.qld.gov.au> To: Michael Smith <msmith@atrad.adelaide.edu.au> Cc: freebsd-chat@freebsd.org, syssgm@dtir.qld.gov.au Subject: Re: 2.2.1 - rumours? Message-ID: <199703250816.SAA11816@ogre.dtir.qld.gov.au>
next in thread | raw e-mail | index | archive | help
Michael Smith <msmith@atrad.adelaide.edu.au> wrote: >... and what you've politely omitted to mention is that it's not for lack >of effort on the part of the people making the release, but rather that >nobody, it seems, has had the _courage_ or _inclination_ to test 2.2, >all of you rather waiting until it was released. Sadly, I am one of the guilty. We have a production system which uses PCI Adaptec 2940 controllers (the ones that had problems in 2.2R) and we always intended to wait for 2.2.1 (but now might wait for 2.2.2). Why? We have no test machine with a similar configuration. High powered PCI SCSI PC's are still rare enough that we have only one of them at our disposal. It is already in use. On the other hand, my 386 test box ironed out a 386 specific problem. :-) It's all that I have available for destructive testing. That's just life. >How can anyone find/fix problems if they're not reported until after >the whole testing phase is finished? True. Most bugs will be in the newest stuff. The newest stuff is often device drivers for the newest hardware. The newest hardware is often expensive, and usually rare. Bummer. I think the secret is to not agonise over it too much, and to plan on having minor bug-fix updates. It's pretty much inevitable. Stephen.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199703250816.SAA11816>