Terms "pre-production" and "production" might not be best in context of automatic client upgrades
Although we use term "piloting" in the package name, and there are references to term "staging" internally (database) as well, for UI/settings we are using term "pre-production". Althoug same "instance" of SCCM implementation/hierarchy can be used to manage multiple environments (development, QA, pre-production, production etc.) using term "pre-production" within the same instance of SCCM implementation/hierarchy can be confusing since it's technically still the same SCCM environment (whereas "pre-production" implies a different environement). This is especially confusing for customers who have separate/isolated SCCM instances/hierarchies managing their pre-production environments (DEV, QA, etc.).
Therefore, the suggestion is to replace use of term "pre-production" and possibly "production" with different terms. One idea would be to align them with Windows/Office and use terms "targeted' or "pilot" and "broad" or "main".
This way, customers with individual/isolated environments would all have a pilot and broad client deployment in each environment as opposed to an environment that is considered production having a pre-production (and production) client deployment and environments that are considered pre-production having (pre-production and) production client deployment.