❓ Niche software versioning question
Does anyone have favourite examples of software versioning schemes?
I may or may not be thinking about changing CryptPad's versioning system and I'm looking for alternatives. I like Ubuntu's date-versions (e.g. 20.04, 21.10) but we're on a different scale.
Also there's so much to take into account: our workload, incentives to ship features, 3rd party admins who apply updates, marketing of new features, etc
HMU if you have some examples (or own work) that you like!
❓ Niche software versioning question
@MacLemon @freebliss There's a range of reasons why we are considering this change. Everything from our workload changing away from bi-weekly releases (to longer gaps), to better promotion (4.0 got some interest, minor releases don't), to managing/updating dedicated instances with paid support (which we want/need to do more of).
The current versioning scheme feels arbitrary and does not do a good job at reflecting how CryptPad is changing, its main reason for being there is that it's already there. I like the idea of dated releases a la ubuntu eg. to help identify how long ago an instance was updated. This is all speculative for now btw, I was just fishing for examples to look at.