After some hours of thinking - in my humble opinion a autoupdate feature 
could break too much. Not only that there could features changed, removed 
or added that could break the users spam fighting, there are also some 
important dependencies for the used (or not) plugins. It is so easy to 
configure the notify feature and to get an email about new versions (a 
text line is added to the GUI in 0.6.03), to open the GUI and to click on 
the link in top menu -> download the new assp.pl directly in to the base 
dir -> if autorestart and the assp.pl - change - watching is configured, 
assp will do an automatic syntax check and restart.

I don't like the idea to restrict users of outdated versions from using 
Griplist or anything else. If the public version is out, anyone is free to 
use the version he like. For the current RC it would be nice, if most 
'testers' upgrade to the latest version. On Fritz's webpage is the change 
log (thanks Fritz), if you want to know, what has changed and what is 
fixed in which version.

Thomas





Scott MacLean <a...@hollsco.com> 
25.11.2009 19:38
Bitte antworten an
ASSP development mailing list <assp-test@lists.sourceforge.net>


An
ASSP development mailing list <assp-test@lists.sourceforge.net>
Kopie

Thema
Re: [Assp-test] used V 2.0.1 versions






As long as it's not forced - my big server that handles thousands of 
mailboxes and hundreds of thousands of emails a day - I can't afford 
for it to go down for any reason, so I would want it to be done 
manually. My small server that handles only a few clients and who are 
understanding if their mail goes down for an hour or so - no problem 
with auto updates there. I typically try the new versions there 
first, and if all is well for a couple of days, I update my big box.

At 11:46 AM 11/25/2009, K Post wrote:

>I'd like to chime in that I don't think autoupdates are the way to go.
>First, for those of us who have made minor modifications to ASSP for
>internal reasons (long story), this would be a huge problem.  Second, if
>autoupdates are forced, I think you'll actually decrease the number of
>installations - there's plenty of real organizations (unlike our 
non-profit)
>that can't stay on the bleeding edge and need to do QA testing on their
>own.  I definitely saw this in my former life in corporate America.
------------------------------------------------------------------------------
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




DISCLAIMER:
*******************************************************
This email and any files transmitted with it may be confidential, legally 
privileged and protected in law and are intended solely for the use of the 

individual to whom it is addressed.
This email was multiple times scanned for viruses. There should be no 
known virus in this email!
*******************************************************


------------------------------------------------------------------------------
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

Reply via email to