Question about update strategy in the same branch?

[alambiki]

Hi everybody,

We have installed Elastix 2.3.0 version on many customers servers.
On a regular basis, Elastix releases updates in this branch via "yum update"
What is the "state of the Art" concerning updating.

1/ Do we have to update all of our customers using a "Yum update" command ?
2/ Or do you recommand to do "nothing" since the customer does not complain about anything ?
3/ If you perform a new installation, do you recommand to perform a Yum update ? My technicians tell me that they prefer to stay in a previous and installed version (thus old). That helps them to troubleshoot problems with the same version installed at our customer premises.

Thank you for your advised replies.

 

[soborno]

Hi,

That's a good question...
And there isn't really an answer to that...
It will depend of a number of factors,

First, for security reasons, it's probably best to have the latest stable (and also, probably has more bugs fixed), and for a system open to Internet, probably the best.
You also have the more up-to-date drivers for the devices you can use..

Also, there are systems that are hard to update, like some production sites, for instance in the health business, and since any upgrade has some work to do, could be a problem.
Also, if you do some "custom code", any upgrade could be a problem...

Be careful of what technicians tell you, many times they like to stick on what they already know... And that can stop you from growing.

To sum up, is probably the best to upgrade your systems (in stable version that you tested well also) on regular basis (probably not every upgrade that appear...), so your costumers can take the most of the product; what you will encounters some cases when it's not recommended

Regards,
Claudio

 

[alambiki]

Hi claudio,

Thank you for your reply.
I will think of upgrading the system of the same version, only if we did not customized the code or the configuration.
bye