Version-specific channels in OperatorHub

[jgawor]

Feature Request

Is your feature request related to a problem?

The appsody-operator is published under the beta channel in OperatorHub. With a single beta channel we don't really know what version of the operator we will get today vs 3 weeks from today. In order to have some stability, it would be nice to have additional channels per each release such as 0.2 or 0.3 which would point to the latest patch release of a given line.

Describe the solution you'd like

Publish version-specific channels to OperatorHub so that other projects such as Kabanero can have better control over Appsody Operator versions they get.

[leochr]

@jgawor Having a separate channel is a good idea. To avoid cluttering, we think it'll be appropriate for major releases (e.g beta, 1.0, 2.0). We don't anticipate to have patch releases for minor releases - 0.2.0 was an exception since our release cycle didn't quite align with others, so we had to make changes based on the feedback. Going forward, we plan to have a release candidate before the release - which will allow those who consume our operators to provide feedback.