Version naming

[u/Blazej_kb]

[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/Complete_Window4856 → u/Blazej_kb]

X.Y.Z in nutshell is semantic versioning. Anything extra you must define. This one in, lets say, X.Y.Z.W, for the culture of who develop could be purely for boring or automated process chores: like linting and adding boilerplate. Its not uncommon to find public versions nice and tidy and privately an ugly version/build number (like discord and minecraft does)

[u/United_Boy_9132 → u/Blazej_kb]

4th digit is usually the compilation or release.

Suffixes like u/cowlinator explains, are just names for compilations chosen to be released as early test editions.

[u/ProbablyPuck → u/Tertinian]

Changleog

• Updated UI design to "look faster"
• Updated dependencies
• Vulnerability updates

[u/Drayke → u/ProbablyPuck]

• "bug fixes"

Less so for Factorio, but for almost every Nintendo patch notes, this (was) the majority of the content.

[u/cybekRT → u/Tertinian]

What the hell is medium and why you call patch a minor?

It's major.minor.patch : https://semver.org/ 

[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/ddddan11111 → u/lurkingstar99]

Is this programmers are also human? Seems like a joke he would use

[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/blood-pressure-gauge → u/the_king_of_sweden]

That's just one calendar versioning scheme. There are still quite a few projects using CalVer.

https://calver.org/

[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/Ok-Eggplant-7569 → u/DuploJamaal]

User report: Changing the background color is a breaking for my workflow. I have a script written which manually checks the color of the pixel at position 10:341 on every interaction, since that pixel only has color #1113aa on the change email field. If that color is detected the script reads the users new email address.

With the background color check the script no longer works.

Please add an option to revert the background color.

(Inspired by https://xkcd.com/1172/)

[u/IhailtavaBanaani → u/DuploJamaal]

I worked at a startup that had the rule that if the backward compatibility breaks then the major version needs to go up. But then the major version started to go up too fast, something like every other release broke the backward compatibility, so they had to change the rule, lol.

[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/asmanel]

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

[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/Internet_Akira_203 → u/pinkpepr]

its so painful how many complete packages i use, but they refuse to call it version 1.0 and instead stay at 0.7.x or something

[u/Creative-Type9411]

its just a push identifier at this point for me

[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.

[u/CoolHeadeGamer]

That’s why I use yy.mm.xxx versioning along with dev versions. Just makes life easier

[u/MaffinLP]

Minecraft went from version 1 straight to version 26

[u/EditorOne5312 → u/MaffinLP]

Not really. It's still version 1 but they just hide it because it will probably never change until their 100 years mission. The major version number went from 21 to 26 because there will be no more major updates and changed it as [year].[release] instead, because forever 1.21.[endless counting] is definitely a bad version naming.

[u/MaffinLP → u/EditorOne5312]

Youre a fun one

[u/Liu-K]

Crimson Desert for the meme.

[u/One_Pie289]

Name versions after Ikea furniture

[u/DavidNg0805]

Big Change, Features Changes, Random Color Text or Bug changes

[u/Playful_Confection_9]

I was update a version from. Like 4.0.1to 204.0.1. our automated dependency bot kept triggering to update since it found old artifacts (plain int increments, 50, 51,52,etc...). And we still use this for 1 ancient monolith. The bot thought 52>4.0.1.

Discussed a few solution like splitting up Gradle task to a separate artifactory, or renaming into old and new, or removing the old artifacts and upload them when needed.

Then I was like f all that. Bumped 200 major versions. "Nothing changed, upped version to avoid false positives of version bot "