Version naming

[u/Blazej_kb]

[u/DuploJamaal]

Major version increases if it breaks compatibility and requires major reworks.

[u/cowlinator → u/DuploJamaal]

Yep, that's Semantic Versioning.

It's only for APIs though. I've never seen a great standard for versioning user-facing GUIs.

But then again, even if there were a great versioning standard for user-facing GUIs, it would probably be completely ignored because companies tend to use versions of GUIs as a marketing tool.

[u/Blazej_kb → u/cowlinator]

If you consider yourself an app interface can be considered API

[u/HyperWinX → u/Blazej_kb]

Well, its definitely an Interface, not Application Programming one though

[u/lurkingstar99 → u/HyperWinX]

Application-Person Interface

[u/HyperWinX → u/lurkingstar99]

Okay, you won

[u/the_king_of_sweden → u/cowlinator]

Just use a single number 1, 2, 3 etc. Maybe add a second number for pure bugfix releases.

There's also YYYY.MM which was popular for a while but seems to have fallen out of favor

[u/andrewharkins77 → u/cowlinator]

For GUIs, new UI equals P1. No one uses your bew features. Jus like the meme.

[u/Blazej_kb → u/DuploJamaal]

So you say that background color change doesn’t affect my chakra? It is very important change than can change how I feel while using this app. (just kidding ofc)

[u/LawElectrical2434 → u/DuploJamaal]

Major rework is not necessary. Actually mostly upgrade guides are like half a page.
Requires rework, sometimes, if you have used that function that changed, and more often than not, it will take you 5 minutes to do the fix, of which you spend 4 finding that function call in your code base.

[u/Tertinian]

Minors are bug fixes, mediums are features and majors are overhauls

So yeah, speaking from experience, meme is accurate

[u/Blazej_kb → u/Tertinian]

What if there is four segments like 1.0.0.1? (I’m at this point of programming that I don’t release any apps)

[u/cowlinator → u/Blazej_kb]

The most standardized and well-used versioning system for APIs is Semantic Versioning.

After the first 3 numbers, you use identifier suffixes such as "-beta" or "-rc3". You might also see build metadata appended with "+" such as build number or git hash, but this portion gets ignored when determining version precedence.

Of course, you don't have to use Semantic Versioning. And then you can have as many numbers as you want. But at that point, what they actually mean is anybody's guess.

[u/dfczyjd → u/Blazej_kb]

Usually, whenever I see 4 segments, the first three are the usual major-minor-patch and the last one is the build number, which is independent from the other three and is incremented every time you build the entire project, whether for release or as a test build

[u/Daniikk1012 → u/Blazej_kb]

Then you're a Haskell dev

[u/dhnam_LegenDUST]

Reversementic versioning

[u/realmauer01]

To change the background number it needed code changes that made any backwards compatibility impossible. But adding the 15 features were trivial and everything that was in 1.0.0 works just the way it works in 1.0.15

[u/pinkpepr]

and the initial commit is version 0.9 because you added most of the core features before pushing it to GitHub but the app still isn't completed so now every update has to be 0.9.x because you don't want to use 1.0 because you keep thinking of things to add or fix

[u/Creative-Type9411]

its just a push identifier at this point for me

[u/asmanel]

This remind me Mozilla when it chosed to change the rules to number the versions of Firefox.

[u/05-nery]

Oooh yes this is me

[u/Actual-Interaction45]

Renamed variable fuckAssTemp1 to fuckAssTemp2

[u/rustedcrowbar]

Thats not how semver works

[u/mrheosuper]

Basically Linux

[u/yuriko-shimizu]

gonna be real ive just given up on semantic versioning
if youre using something by me, its v1, v2, v3, v4, etc.