EA Build updates - risks ?

[mikewhit]

I am naturally cautious about 'upgrades' in the absence of an absolute show-stopping bug, and I have a project manager similarly risk-averse (particularly mid-project).

We are running 4.1 build 731, has anyone had any problems in going from an earlier version of 4.1 to a later version, particularly in terms of model integrity, or is this a completely risk-free (;-) process ?

Can you have (slightly) different versions accessing the repository, or is it an all-or-nothing affair ?

And are there any compelling improvements ?

Thanks.

[thomaskilian]

mikewhit,
I always upgrade as soon as possible and I never had any show stopper. Just the opposite, each release of EA brings more usefull features. On the other side there are still so many features I never ever endeavoured. If you're still happy and don't run in any bug you could shurely stay with your current version. If you're going to upgrade: have all of your users upgrade to the desired release. Once I had problems with one user running an older release where it crashed under certain circumstances. Upgrading resolved that problem.

[Barry_Pearce]

We also upgrade imediately - now running 4.10.739 started with 3.60.something!

Never had a problem..

[mikewhit]

Thanks, that's what I needed to hear !

I too would like to use new features or ones that have been 'fixed', and I have just reported an EA bug which was actually fixed in 738, so they're obviously ahead of the game, as long as we keep up!

I suppose I've had my fingers burnt in the past by e.g. driver updates, and have subscribed to the 'if it ain't broke' philosophy.

It's a little more serious when you have an entire project's modelling within a tool, and I didn't want to be the one who recommended the change that trashed the database !!!

Thanks again.

PS Thomas, congrats on your Guruship ;-)

[thomaskilian]