As a customer and user of RHOSO, the versioning schema is currently unclear to me.

I understand that RHOSO is the Red Hat product for OpenStack 18 (Red Hat OpenStack Services on OpenShift 18.0) and is documented as such: https://docs.redhat.com/en/documentation/red_hat_openstack_services_on_openshift/18.0/html/release_notes/index

However, I don't seem to be able to install such a version in my OpenShift cluster from the OperatorHub Marketplace:

I can only select "stable-v1" update channel and as well as individual versions such as "1.0.x".

I would expect that here I can select an update channel such as "stable-18" or "18.0".

Furthermore, once the operator is installed, it is not actually clear to me as the user which version I have installed. The "Installed Operators" section in my OpenShift cluster lists the following:

All of this does not match the versioning expressed in the product documentation, which talks about "RHOSO 18.0.6 (Feature Release 2)" in the release notes: https://docs.redhat.com/en/documentation/red_hat_openstack_services_on_openshift/18.0/html-single/release_notes/index#chap-top-new-features_release-notes

Finally, it is not clear to me as an operator which care and prerequisites I need to take when updating from one version to another (e.g. 1.0.8 -> 1.0.9 or 18.0.4 -> 18.0.6). Are there potentially breaking changes? Should I expect downtime? Can I perform this procedure on a Friday afternoon?

It would be great if these points can be addressed (either by aligning the various versioning schemes or explicitly documenting them in product documentation).

Thanks.