* aCaB wrote: > G.W. Haywood wrote: >> I suspect that rather than QA, what you do is just a lot of hap-hazard >> testing. That's why, whenever I see a new release of ClamAV, first I >> will suppress a groan and then, before I risk it on any of my servers, >> I'll wait a while and watch the users' list to see how much trouble it >> causes. This approach serves me well, although I can't say I'm proud >> of the fact that I'm letting a lot of poor innocents do my acceptance >> testing for me. > > Hi G.W. Haywood, > > My mail was about custom databases provided by 3rd parties, not about > ClamAV release cycles. > > Besides, you miss another point: ClamAV is an open source software, > consisting of roughly 150K lines of C code and 650000 signatures, > currently maintained by three full time developers, one and a half full > time sigmakers and a system administrator. > So less than 6 people maintain Clamav.
I'm impressed. Cut these guys some slack. They can't do everything. Thats the beauty of Open Source. If you don't like it FIX IT. If you can't fix it, report that its broken. If possible Where is it broken, why is it borken, and how it might be fixed. If you can't do that, Get a commercial solution. Freedom isn't free. ( from effort or errors ) -- Sincerely, Nathan Gibbs Systems Administrator Christ Media http://www.cmpublishers.com
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
