Style Number Release For Free

0.1.0 is a work in progress, you can expect that this software is not stable or should be used on production environments. new versions are likely to break functionality. 1.0.0 is the first stable release. 1.1. 0 is the first feature release.

First Number: This is the major release number and indicates major incompatible changes or additions to the product. Second Number: This is the minor release number and indicates minor changes to the product, or improvements to a functionality.

The official "semver" semantic versioning scheme describes a system of MAJOR. MINOR. PATCH version, where a MAJOR version bump involves breaking changes, a MINOR version bump adds functionality without breaking anything, and a PATCH version provides bug fixes (to existing functionality) that don't break anything.

Modern computer software is often tracked using two different software versioning schemes: an internal version number that may be incremented many times in a single day, such as a revision control number, and a release version that typically changes far less often, such as semantic versioning or a project code name.

A normal version number MUST take the form X.Y.Z where X, Y, and Z are non-negative integers, and MUST NOT contain leading zeroes. X is the major version, Y is the minor version, and Z is the patch version. Each element MUST increase numerically.

Release numbers are used to record the preauthorized order numbers for a product being delivered. Release numbers specify the order number, quantity, and status.

First Number: Tracks major changes. Second Number: Tracks minor changes. Third Number: Tracks patches or mere bug fixes. Fourth Number: Tracks changes less significant than a patch.

Version numbers are usually divided into sets of numbers, separated by decimal points. Typically, a change in the leftmost number indicates a major change in the software or driver. Changes in the rightmost number often indicate a minor change. Changes in other numbers represent varying degrees of changes.

Numbering each version helps to distinguish one version from another. It may be suitable, simply to number each version, regardless of the changes, using consecutive whole numbers e.g. V 1.0; V 2.0; V 3.0 etc. to track which version of the document is being worked on.

For example, if the latest version number of a software is 1.17. 10 then each number (i.e., 1 & 17 & 10), indicate a different information related to the same product. You must also note that a version name is not the same as a version number. For instance, Google Chrome Version 83.0.