How is Legend versioned?

[pedroleaoc]

Hey folks, quick one here: How is Legend versioned? By release date? ie "Legend version 2022-04-05"

I am working with the folks charming Legend and we wanted to represent the Legend version in the charm's semantic channels. The way we usually do this is by creating different tracks to major versions and expressing the minor releases through risks (channel=track/risk). For instance:

• The charm for app_name v5.0 has it's own channel --channel=5/stable or depending on the application it can be even --channel=5.1/stable, --channel=5.2/stable etc.

Using this system ensures that folks deploying the application know exactly what version they are in. In the case of Juju, to install v5.0 you would run juju deploy app_name --channel=5.0/stable. To upgrade the application, you would run juju refresh app_name --channel=5.1/stable. This way you automatically get bug fixes and security patches as minor releases, but must explicitly declare new major versions. This prevents accidental compatibility issues in production.

Now for Legend, we can create one track per release, but that would lock someone in a version and not give them the minor releases.

Finally, Juju or not, I guess that my question is: do you folks currently express major/minor releases somehow via the version date?