Use CalVer

[micheljung]

The client currently (kinda) uses semantic versioning. This is good for APIs - which the client isn't. To the user, semantic versions don't mean much, and looking at a version number, he has no idea how current the version is.

Using CalVer, like e. g. IntelliJ does (e.g. 2020.1), versions would become a bit more user-friendly.

Opinions?

[1-alex98]

That does need code adjustments as well

[Katharsas]

I doubt the advantages justify the cost of change. Contributers/testers are used to the current schema.

[micheljung]

The schema itself doesn't change: x.y[.z] and we could always go for an explicit x.y.z

It would simply be e.g. 2020.6.0 instead of 1.1.8

[Sheikah45]

With the next release we will probably be switching to Calver as it helps to give a sense of how old any client is and the current versioning code supports it.

Having surveyed some of the devs there seemed to be no push back.

I intend to use the format YYYY.MM.Minor-qualifier