this post was submitted on 07 Jun 2024
286 points (99.7% liked)
Announcements
23326 readers
1 users here now
Official announcements from the Lemmy project. Subscribe to this community or add it to your RSS reader in order to be notified about new releases and important updates.
You can also find major news on join-lemmy.org
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
That's my bad really. Currently we're using the patch semver to denote non-breaking changes, and the minor for breaking.
We're holding off on a major release until the API reaches stable, which like all open source projects we're reticent to do because then it puts a lot of pressure on us to match the standard of enterprise-level software developed by a large corporation.
Even though lemmy has many thousands of monthly active users, we're still really an beta-level software developed by a handful of people.
Honestly, that strategy feels like the most sensible one, since the real world often does not (or can not afford to) care to wait for v1.0.0 before using software. It's no wonder so many programming ecosystems have adopted it.
I find it a bit of a shame it's not part of the semver specification itself, which only states:
My point is, I don't think that's "your bad." It's just how it is, and the best there currently is. Unless you think there's something that could've been done better, in which case I'm curious as to what, if you're willing to share.