Jerry wrote: > > On Fri, 03 Oct 2008 22:12:49 -0700 > John Rudd <[EMAIL PROTECTED]> wrote: > > > > >At the very least, when the config file and options change, the ClamAV > >team should post a notice which explicitly lists (and only lists): > > > >1) new config items > >2) removed config items > >3) config items whose syntax, semantics, or options changed, and how > >4) supported but deprecated items, and what, if anything, replaced them > > > >This shouldn't just be buried in release notes, a read me file, or a > >change log. It should be in those places _TOO_, but it should also > >exist as its own stand-alone statement that any one of us can easily > >see and find. > > From my experience, if an end user refuses to RTFM, adding additional > reading material is not going to solve the problem. The needed > documentation is all ready readily available. The motivation to fetch > and read it are what is sorely lacking.
I disagree. I think this would be VERY useful. Not for the people who don't want to RTFM, but for the people who would rather not have to wade through the docs and changelog to figure out if there are config changes. However, doesn't this already exist with the upgrade notes? Take a look here: https://wiki.clamav.net/Main/UpgradeNotes093 I don't know if they are this detailed on all of the releases (the notes for 0.94 don't say much), but this looks like exactly what John was asking for. -- Bowie _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
