Bug 1373502

Summary: [RFE] Can we have more meaningful version numbering for the content views?
Product: Red Hat Satellite Reporter: Rick Dixon <rdixon>
Component: Content ViewsAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: 6.2.0CC: bbuckingham, bkearney, rdixon
Target Milestone: UnspecifiedKeywords: FutureFeature
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-06-01 19:44:40 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Comment 1 Brad Buckingham 2016-09-12 14:36:27 UTC 
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.
Comment 2 Rick Dixon 2016-10-13 13:18:37 UTC 
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
Comment 3 Bryan Kearney 2017-06-01 19:44:40 UTC 
Based on comment 2, I am closing this out. If this was done incorrectly, please feel free to re-open with additional information.