Upgrades - not if but when?

Good Day cooner:

Yes, we all have the same idea; but then real life pressures blow up
the plan.
Do sooner because you need the fix or enhancement.
Do later because you have no time and things are working - Not
Broke-don't fix.
Contract says you cannot get more then two behind or support is
affected.



len.hartka@...



________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of cooner_55421
Sent: Saturday, October 30, 2010 2:50 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Upgrades - not if but when?




Hi,

A lot of recent posts on upgrades and support contracts.
It's always a hotly debated topic.

Any of you have a policy about patch and upgrade regularity?
How often do you plan your patches, upgrades?
How do you plan your support?

I used to think you should upgrade software every five years.
Patch once a year unless something critical comes up sooner.
Support is perpetual but maybe negotiable rates depending on where you
are in the upgrade cycle.

Just wondering about other peoples ideas.

Thanks






This e-mail and any attachments may contain proprietary and/or confidential information. If you are not the intended recipient, please notify the sender immediately by reply e-mail or at 410-472-2900 and then delete the message without using, disseminating, or copying this message or any portion thereof. With e-mail communications you are urged to protect against viruses.


[Non-text portions of this message have been removed]