The current behavior is the following:

1. publishing a new version of a content view, increments the major version (e.g. 1.0, 2.0, 3.0...etc)

2. publishing an incremental update of a content view, increments the minor version (e.g. 2.1, 2.2, 2.3...etc)

Does that help?

In addition, when publishing a new version of a content view, the user can provide a description which may help with identification of what a particular version represents.

Hi Brad,

Yes, that was very helpful. I sent the customer the steps to accomplish this outlined in the below document (I did not see more detailed steps in our installation/user guides):

~~~
The process for creating incremental updates is outlined below (page 279):

   10 Steps to Build an SOE: 10 Steps to Build an SOE - How Red Hat Satellite 6 Supports Setting up a Standard Operating Environment
   Use Case 4: Incremental Updates - Apply Selected Errata to Hosts
   
   https://access.redhat.com/sites/default/files/pages/attachments/2015-10_Steps_to_Build_a_Standard_Operating_Environment.pdf
~~~

Thank you again for your assistance with this.

Rick

Based on comment 2, I am closing this out. If this was done incorrectly, please feel free to re-open with additional information.