Why do software updates skip numbers. E.g. 1.17 to 1.34?

712 views
0

Why do software updates skip numbers. E.g. 1.17 to 1.34?

In: Technology

[removed]

There will be internal versions of builds that may not be ready to release into the wild due to bugs or incomplete features. You need to keep track all versions for tracking and QC

Everytime the programmers change the program, they will increase the version number. For example, adding a single capital “A” to a paragraph may result in the version number going from 1.17 to 1.18.

Now, after a few weeks, a lot of edits have been made, and now we are at 1.34, and maybe the app now has a new feature, like voice messaging. The programmers say “alright, there’s enough here that we ought to update everyone’s apps”, so they push the update through, and now you’ve skipped from 1.17 to 1.34

There are some standards out there but only loosely followed as anyone can make up their own scheme. For example in the open source world public releases are usually even, and pre-releases are odd. Going from 0.12 to 0.13 will be backwards compatible, but going from 1.8 to 2.0 will have breaking changes. These are “major” releases vs “minor” releases.

If you’re interested in the details see https://semver.org/