On Nov 26, 2009, at 8:42 AM, GrayHat wrote: > Yeah, I think it may be reasonable; and a good default > may be "download, don't install, notify" (with notification > repeated at every "rebuildspamdb" btw - so lazy-assed > admins won't forget about it :D)
Hello GreyHat, If it must have auto update, I do agree, download, do not install, and notify. Further, I would have one click activations to new versions. All versions show in a html select menu, and you can change which one you want to use from new to previous all the way back as far as you want to go. This would mean, bringing some sanity to the versioning scheme so users can see a versioning scheme they are familiar with. This was brought up the other day. Your joking comment about "lazy-assed admins" is actually an excellent point. I understand you were kidding, of course, but I think we need to keep in mind, that maybe there is a chance this is problem is not related to lazy admins at all. I see it being a possibility of a few things 1) Lazy ass admins :D 2) If it aint broke, don't fix it 3) Too rapid a release cycle, way too rapid, maybe they are not lazy, but too busy ass admins :) 4) Even somewhat seasoned perl coders on the list meet resistance in reporting issues, think how the non seasoned perl coders are going to feel. Thats all I have for now. -- Scott * If you contact me off list replace talklists@ with scott@ * ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Assp-test mailing list Assp-test@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-test
