[Spike] External OLM releases require sequential versioning?

Summary

as discussed in thread #993 (comment 1247837000) We have discovered that external OLM repos for the moment require releases to be sequential.

To accommodate for that we would have to:

• create an ADR record documenting our decision to always publish versions sequentially (no back-dating)
• extend "release issue" template to make sure that prior to each release we make sure previous releases got published

Background

Some excerpts from feedback we've received:

You MUST publish them in order, because the OLM won't allow you to add operators with a lower version number if a higher version number already exists for a given channel in the OperatorHub.

Some partners use separate channels for all releases in a minor version (since the major version here in your example is 0).

Details on creating an update graph with OLM are given here: https://olm.operatorframework.io/docs/concepts/olm-architecture/operator-catalog/creating-an-update-graph/

As for channel naming and crossing channels, see https://olm.operatorframework.io/docs/best-practices/channel-naming/ for info on this. ... dependency resolution had good diagrams that explain the process.