Showing posts from December, 2019

Change of MHU Version String Definition

After defining the version strings in Januar and a look back I decided to change the version string definitions and use the common way of version counting.

In Wikipedia the definition major.minor[.maintenance[.build]]  looks good and is similar to my current definition: <core>.<major>.<minor>[.<hotfix>]

So I will remove the core component because it was not changing in the last 10 years and add the hotfix component as non optional part of the version string. By the way I will do the same as the big players - removing the unused parts from version string like java 1.8 is becoming Java 8.

To migrate all the projects I will remove the first number for the next iteration. So mhu-lib 3.6.3 will be 6.3.0 after the next release. The next snapshot is 6.4.0-SNAPSHOT.

10.Jan.2019 - MHU Version String Definition

In the last years I see a wide range of different version string definitions. In the last years more and more one digit only versioning becoming more and more popular. See also Wikipedia.

I prefer the notation with three or more numbers but in a different meaning as common: <core>.<major>.<minor>[.<hotfix>]

The core version describes a common structure or technology change. Most of the time it's the same. The core version only changes if the central structure or idea is changed. E.g. if switching from 'all in one' to a modular architecture.

The major version will increase if for example all dependencies are updated and the project must be reorganised therefore.

The minor version will change for every bundle of hot fixes and changes.

The hotfix version will only be set if a small important fix is needed without to update the hole project.