Christopher X. Candreva wrote: > It IS a 0.x release. Once he hit 1.x I'll be a lot less forgiving, but as > long as we're at 0.x I expect this sort of thing -- and still think it's > better than the next best alternative.
Plenty of things have yet to go past 0.x and are many many years old. Considering Clam is in really abundant use I think version numbers are little excuse, so it would be nice if sysadmins didn't get kicked in the groin every time a release happens and they forget (or simply don't have time) to read the changelog. What really made me post this is the fact that it has happened several times this year now. I can remember at least 3 major config file changes which happened without warning and were horribly ungraceful. This is made worse by the 'stable' version in Debian Etch committing suicide the instant it grabs the new definitions from FreshClam, forcing us to use the volatile releases. This is really the root of the problem, since a blind 'aptitude update; aptitude upgrade' then causes very big problems. Clearly this hasn't been brought up much before though, so I'll be forgiving on that basis. Or _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
