Lagoon numbering

[tobybellwood]

Currently Lagoon is numbered based on the releases in this repository (https://github.com/uselagoon/lagoon/releases) - i.e. the most recent release is v2.16.0 (at the time of writing).

Confusing, this is actually installed via a helm chart - lagoon-core 1.37.0 (https://github.com/uselagoon/lagoon-charts/releases/tag/lagoon-core-1.37.0)

Although both components are technically using SemVer, we don't strictly adhere to the SemVer spec - we have probably headed towards MarVer ™️ for this repo - we have a big bang release for a new feature in the "major" and then use "minors" to denote breaking changes, or periodic updates. Where we have to patch/hotfix a release before/between new releases, we release a "patch".

As the components that make up Lagoon Core increasingly come from different repositories (lagoon-ui, opensearch-sync, ssh-portal, insights-handler) - the concept of "one release to rule them all" 💍 is less than ideal, and leaves us with some work to do to keep a "release together" - this leads to this.

What we've discussed as a team is to try and find a better solution. I'll outline some options/opportunities below!

[tobybellwood]

lagoon-core and components as CalVer:

We aleady use CalVer in lagoon-images - it's really handy for getting a real-time view on how up-to-date a component is
https://calver.org/

[tobybellwood]

lagoon-charts as strict Semver:

Using strict semver in the charts would mean a frequent major bump every time there is a change that requires user input to install the release - i.e. an updated value, extra field, deprecated config etc