Programming

16971 readers

198 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

Question: Does the build number always increment no matter the version or does the build number resets to 1 for every new version? (programming.dev)

submitted 2 months ago* (last edited 2 months ago) by MortySmith@programming.dev to c/programming@programming.dev

20 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] sxan@midwest.social 2 points 2 months ago

I'm with you; I prefer date versioning for many things. Semver does work really well for things with exposed APIs; it's a stretch to justify using them with user tools, and especially GUI tools. Semver is used to great effect in Go - which is how it should be use: mainly by the language's module management system. Outside of that, it's human readable, but like XML, its main value is to machines, and only secondarily to humans.

Calendar versioning is far more human-oriented, and so more useful for things without exposed APIs or module tooling.