Feature Request Overview

use OLM channels and semantic "minor" version bumps for each RHOSO feature release

Business justification

Our current versioning scheme only bumps the "patch" number incrementally regardless if the release is on the same maintenance branch or a new one. Ideally each FR release would increment the "minor" version number and get deployed in a net new OLM channel. The benefit of this approach is that unplanned maintainence releases can be delivered to customers. Currently we are constrained to using only manual "one off" hotfixes for maintenance branches which must be manually applied by the customer. Leveraging OLM channels and making a slight adjustment to our versioning scheme would be a significant improvement (and less risky) way to deliver to our customers. 

Functional requirements (mandatory - Complete while in New status){_}
{}What do you want the result of this feature to be? Add as many requirements as needed.{_}

• Use a separate OLM channel to release each new RHOSO feature release
• Each channel should have unique "minor" version numbers. For example 18.4.0 for FR4, 18.5.0 for FR5.
• Then we can easily cut and plan for maintenance release to channels which our customers are still using.

Describe the customer impact

Maintenance branch fixes are easier, and safer to apply. As customer base grows this will be extremely important.

There is prior art for this with other products: