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.
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.
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.
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.
I’d be good with that.
So are you saying we are gonna get monthly updates 👀👀
I’d like that, we just have to be more disciplined about not adding breaking changes too often.
Take your time
I agree that there shouldn’t be official names for versions.