Description of problem:

The wording used to describe moving content view versions between
different environment is "promote", yet the activity that takes
place is more of a publication/presentation/association of the 
version with an environment.

For example, if you have a CV with versions 1, 2 and 3 in the
following environments

version 3 - env A
version 2 - env B
version 2 - env C
version 1 - env D

First you promote version 3 to environment B, which leaves you with

version 3 - env A & B
version 2 - env C
version 1 - env D

if you identify an issue with version 3 in env B, you have to rollback
to the previous version, which is done by "promoting" version 2 back to
env B. The change from version 3 -> 2 in env B, is not strictly speaking
a "promotion"

This bugzilla is to request consideration of an alternative way of
naming "promote" of CV's to better align with what actually happens

Version-Release number of selected component (if applicable):

6.1.2 - 6.1.4