Programming

17697 readers

375 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 [email protected]

founded 2 years ago

MODERATORS

snowe

Ategon

[email protected]

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

submitted 6 months ago* (last edited 6 months ago) by MortySmith to c/programming

20 comments fedilink hide all child comments

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

[–] [email protected] 18 points 6 months ago (1 children)

@best_username_ever mentioned Semantic Versioning. It's an actual spec. Not everyone follows it, and it doesn't make sense for a lot of things, and far too many people are dogmatic about it. But it's a good thing to read, and it's not long.

A related, but not tightly coupled, spec is Changelog. Used together, and used correctly these two are nice for users.

[–] Kissaki 3 points 6 months ago* (last edited 6 months ago) (2 children)

I really like Calendar Versioning CalVer.

Gives so much more meaning to version numbers. Immediately obvious how old, and from when.

Nobody knows when Firefox 97 released. If it were 22.2 you'd know it's from February 2022.

It doesn't conflict with semver either. You can use y.M.<release>. (I would prefer using yy.MM. but leading 0 is not semver.)

[–] [email protected] 7 points 6 months ago

I really dislike calver for like libraries and apis. For something like Firefox it doesn't matter as much. But for a library? I want to know if this version has breaking changes.

[–] [email protected] 2 points 6 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.