From: K P. <nnt...@gm...> - 2009-11-28 02:09:55
|
No guns here, I only use swords. Micro$oft = evil. Oh wait, I'm running win32 system. Never mind. :) Seriously though, I'm all for discussion and won't ever take offense... I'd rather see Thomas only implement a simple nag screen than waste his time coding all of these options. The MS approach definitely works, In theory at least, their updates are (also theoretically) tested by a whole team of people before they go out and on all sorts of configurations and hardware. ASSP would only have Thomas and maybe Fritz to test on whatever configs they have. What if they miss something? I just can't afford for assp to crash when I'm not around. Autoupdates are just asking for trouble IMHO. FYI, I just put: new\sassp\sversion.*is\savailable\sfor\sdownload\sat\ssourceforge in my notifyRE. Got my first notification via email today when 0.6.4 came out. I'd love to get a changelog emailed - and I think that would help to incentivize admins to upgrade. Still that's extra coding for Thomas. On Thu, Nov 26, 2009 at 11:42 AM, GrayHat <gr...@gm...> wrote: > >> No guns here ;-) > > Well, ok... I had to write that, some folks start GROWLING > when they hear (or read, in this case) "Microsoft" <grin> > >> Good point doing it with similar options as provided by Microsoft. > > 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) > > > ------------------------------------------------------------------------------ > 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 > Ass...@li... > https://lists.sourceforge.net/lists/listinfo/assp-test > |