this post was submitted on 21 Jul 2023
15 points (100.0% liked)
linuxmemes
20762 readers
1911 users here now
I use Arch btw
Sister communities:
- LemmyMemes: Memes
- LemmyShitpost: Anything and everything goes.
- RISA: Star Trek memes and shitposts
Community rules
- Follow the site-wide rules and code of conduct
- Be civil
- Post Linux-related content
- No recent reposts
Please report posts and comments that break these rules!
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Everything should be date-based name releases.
If it’s released April, 2023 it should be 23.04 or similar.
Other schemes are arbitrary.
Change my mind.
How would you differentiate between versions with major api breaks?
Shhh, they don't know what that means, let them live in bliss
Lol. Developers just need to know what date the api changed. Viola.
Gotta know, are you serious or joking here? Follow up question: are you a developer and have you ever worked on a medium+ sized project? The amount of dependencies you end up with is astounding, you can't just "know" when all those APIs changed, that would be a full time job just to stay on top of. And that's not even taking into consideration transitive dependencies. If a library doesn't use semantic versioning, 99% of the time it's correct to avoid it just to save yourself the headache.
Semantic versioning. If I have 1.0.0 and you release 1.1.0 I can be pretty confident it's safe to update. If you release 2.0.0 I need to read the release notes and see what broke.
If I have version July2023 and you release August2023 I have no information about if it's safe to update. That's terrible. That's really bad.
This is for dependency management and maybe apis more than OSs, but in general semantic versioning is a very good system. It should be used often.