> Notifications of new versions will definitely help. Maybe also
> include what has been changed - so we as administrators can be
> motivated to drop everything else and get the upgrade installed?
I was thinking more or less along the same lines; an idea may be
to setup things so that, if ASSP detects a new version it will fetch
(if existing) a "notice" file from the repository and use it for the
update
alert email; that won't overload the server AND will allow the admins
to receive a detailed email (and, if needed, whatever "ALERT")
> 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.
hm... it depends, see, v2 has a modular architecture, so it shouldn't
usually be needed to change the "core"; better creating a plugin and
putting the "custom code" in there imHo (and if possible btw)
>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.
I think that adding an auto-update mechanism would be a good idea
as long as
1) it may be disabled (i.e. options to "just notify" or "notify and
update")
2) the update time may be scheduled so that one may decide to run the
update during some "off-peak" (local) time
------------------------------------------------------------------------------
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
