New versioning scheme for releases

Recently, we've changed our Targetprocess versioning scheme. From January onwards, you'll see new titles for our release blog posts in the following format: v.2101. Read on for more details on this topic.

Previously, our versioning scheme looked like this: 3.13.22-124452 and our release blog post titles included some of the versioning scheme, such as, 3.13.22. That corresponded to the following template: "<system version>.<major version>.<minor version> - <build version>" .

Even though this is a standard versioning scheme, it's a little too technical and does not offer much value to our users. So, we decided to make our versioning scheme more useful and transparent for everyone.

The general versioning template was changed to: <YearMonth>.<build number>.<hotfix number>.<build version>

Take a look at the following example: 2101.1.0.281401. It refers to:

• 2101 - stands for January in 2021 (YYMM)
• 1 - first build of a month (2 = second build of the month, etc.)
• 0 - initial build, not a hotfix (1 = means build contains a hotfix, 2 = two hotfixes, etc.)
• 281401 - sequential build version generated automatically

So, we plan to continue creating blog posts to outline the most valuable changes on monthly basis. The February blog post will have the title of v.2102 and all subsequent release build posts will have the new template, described above.

Thanks for reading.