I believe that @olivhoenen and @SimonPinches are requesting these changes to not subvert the advertised version of omas available on the ITER cluster via linux modules. If these changes are merged and later omas users experience bugs with omas or lack of features for which a tagged version has been released, then the users will be redirected to @SimonPinches or any other person at ITER capable of installing the latest version of omas for the public version. It was also proposed that there be an untagged version available at ITER, which could be kept up to date, separate from the numbered versions. @olivhoenen also suggested that users could do a pip install to their home directory to get a more up to date version; although this risks users not staying up to date, and could lead to trouble and troubleshooting down the road.
I believe that @olivhoenen and @SimonPinches are requesting these changes to not subvert the advertised version of omas available on the ITER cluster via linux modules. If these changes are merged and later omas users experience bugs with omas or lack of features for which a tagged version has been released, then the users will be redirected to @SimonPinches or any other person at ITER capable of installing the latest version of omas for the public version. It was also proposed that there be an untagged version available at ITER, which could be kept up to date, separate from the numbered versions. @olivhoenen also suggested that users could do a
pip installto their home directory to get a more up to date version; although this risks users not staying up to date, and could lead to trouble and troubleshooting down the road.