Alias Program Packages and Updates

[bkircher]

I am in the process of preparing updating our Alias products (e.g. providing them on an accessible network storage, etc.). Please find attached some observations:

• Providing 2GByte chunks of software for every package (Surface, Design) feels strange and a huge step backwards for deploying the software easily if you have a mixed environment. A common installer package as before would be greatly appreciated and reduce wasted time copying, extracting, etc.

• Providing updates without a Readme is not helpful. (What is the "Hotfix4-2" about? Do we have to deploy it? ...)

• Not this big an issue, but nonetheless: During installation, I've received feedback that the "configure"-button is not prominent enough. (Miss this and you install a standalone Version.)

[anand_joshi]

On a single system, if you are trying to install 2 flavours of alias, only additional or different components gets installed.

Core alias files remains untouched and not additionally installed.

[bkircher]

I know, my arguments where of a different kind:

- Having different (yet basically identical) packages is much more hassle to deploy, especially to a bunch of people. (Also, e.g. the update logic is less clear, do I have to install the "4-2" update for every package or only once ...)

- Any download/upgrade should have an associated "Readme" or "What's New".

[digiformer]

i agree...can anyone say what the hotfix4-2 is all about?

Regards

Tobias