On 22.04.2010 06:20, Dennis Peterson wrote: > Suggest at least one way to inform all the users successfully that > obsolete software is going to die soon - and don't let it slip past you > in your solution that the ClamAV people have know way of knowing who > they need to inform. And recall too, this: Filling their logs with > warnings didn't work. Posting the notice on the front page of their > website didn't work. Running commentary in this list didn't work. > Announcing it in their Announcements list didn't work.
Every major software project hits this road block sooner or later and solves it in an acceptable way. This is not rocket science. I am pretty sure some way of versioning support was on the table during the decision making process and was rejected. Knowing the rationale behind it would be nice. I think it was a bad decision but knowing how the decision was made (the other side of the argument so to speak) would help. [...] > We're left with this: The "problem" affected only those that did not pay > adequate attention. There is no cure for that. Our problem statements differ. I am against clamav's "right" to turn off services on other people's computers which does not say anything on sysadmins who may or may not be paying attention. > So here's a message to everyone that was surprised: PAY ATTENTION > because there's going to be a next time! I hope not. -- Eray _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
