The names of previous Lemmy versions were all very boring and repetetive. We need something much more creative. Any ideas?
Eh, if someone on the team is feeling creative I don’t mind fun version numbers but semantic versioning is quite searchable and reduces confusion.
One does not exclude the other. You can have a fancy name and a semantic versioning.
The problem is that it is almost always just one lf them. Let’s say that v0.20 is called “Fuck Spez” and v0.21 is called “YouKnowWhatFuckMuskToo”.
Most people are going to refer to them by either the number or the name, almost never are both used. The biggest problem with names is that they are rarely sortable (google did it with android, for a bit but not anymore), so in the future it is hard to know which is which without resorting to looking at a list of releases.
For example, in the future when we are on v0.30 someone might say “ah, but this has been an issue since “Fuck Spez”.” And then most likely you have to look it up to know what they are talking about. If we coulld force everyone to alwaya write “version “Fuck Spez” (v0.20)” then it would be great, but that never happens.
I personally prefer just semantic versioning for this reason.
I think that’s the case and why I said it’s fine in my OC, but the more I think about it I’m slightly concerned it might cause some fragmentation “Does anyone know how to force a user sync in Lightfoot?” and “How can I sync users (forced) in v13.8.12?”
Yeah it muddles with searching for answers, especially when the names are common things. Apple can get away with naming macOS on places in California, but it’s going to be tough searching “having trouble posting comments on Thor” or whatever. The naming scheme can work, but it has to be very unique
Based on classification? Taken from a Wikipedia article concerning lemmings.
It’s software versioning, not a new breakfast cereal
Motörhead had 23 studio albums.
We’ve been notoriously bad about doing more frequent releases, but if we were to release every month, then naming them could get annoying really quickly.
I’d prefer to just stay with the semantic version numbering, like a lot of projects with a ton of releases do. Like look at react’s releases.
The fun named versioning makes sense for operating systems, that release only like once a year, but not for apps, docker services, libraries, etc.
I’d like that, we just have to be more disciplined about not adding breaking changes too often.
We only do major versions around once a year so those could still be named, while using numbers for minor versions. Lemmy is more user-facing than react, so it would make sense to have a more user-friendly versioning.
