The project version has quite a few fields that relate to the OTAP environment. Often a path, database name or other property changes from one environment to the other.
Project versions have a status, and some statusses imply one OTAP-environment or another.
Would it be a lot of trouble to add OTAP-specific settings at the project level, and declare a project version status for which it is valid?
It still means some editing in case of distributed server environments, but it makes some releases easier to manage.
Best answer by Anne Buit
View original