When to use Major or Minor Upgrades ?
Hi All ,
Are there any best practices followed for Major / Minor upgrades ?
Can we make a generic statement that the organization should always go for Major upgrades ?
The only benefit of Major upgrade I am aware of is it removes a previous version of application and installs a new version . Hence you get an option to install application at a new location which is not available in Minor upgrades ?
Are there any other known advantages of Major upgrade over Minor which makes it a more preferred option during upgrades ?
Any suggestions will be really helpful .
Cheers ,
V
Are there any best practices followed for Major / Minor upgrades ?
Can we make a generic statement that the organization should always go for Major upgrades ?
The only benefit of Major upgrade I am aware of is it removes a previous version of application and installs a new version . Hence you get an option to install application at a new location which is not available in Minor upgrades ?
Are there any other known advantages of Major upgrade over Minor which makes it a more preferred option during upgrades ?
Any suggestions will be really helpful .
Cheers ,
V
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
VikingLoki
18 years ago
I make Major Upgrades whenever possible, just for simplicity sake. Old off, new on, keep it simple. Yes, it's a full uninstall and a full reinstall, but we deploy after hours so... who cares if the deployment time doubles. It really depends on your environment, when & how the upgrades are done, does it interrupt the user or not, etc. If I had users sitting there not able to work while the upgrade takes place, then I'd consider minors. But I don't.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
