Single version proposal

[flavio]

A new take on this problem, as discussed with the rest of the team.

[flavio]

Another possible solution would be to make use of the patch attribute of the universal stack version.

Pros:

• All the components have the same version. The appVersion inside of the helm chart is reflecting the version of all the container images

Cons:

• A small fix to a single component triggers the release of all the others.
• Users might get the feeling to update their cluster because a new patch release has been tagged, but actually no change has been done to the components running inside of the cluster.

We would need to invest more time and efforts into automating the whole release "overlord orchestrator" or just build up fixes and push them once they reach a certain mass.

Honestly, I have mixed feelings about this approach. That why I excluded that from the proposal. However, we could also start with this proposal and later make use of the patch attribute.

[flavio]

@kubewarden/kubewarden-developers I've updated the document to reflect the feedback emerged during the review process. I've resolved all the comments you left over there.

For the ones that are still open, I prefer to have the commenter close the issue as solved or provide more feedback.

Thanks to everybody