Are there any know plans for version numbering logic?
Like 12.0.0.1420 was RMT and then 12.0.0.1420 P20230223, 12.0.0.1420 P20230412 and 12.0.0.1420 P20230718, so we needed to change our monitoring script solutions to not only check 12.0.0.1420, but also Pxxx.
Now with 12.1 first it was 12.1.0.2131 and latest 12.1.1.56. What would be the next version 12.1.1.x , 12.1.2 or 12.2?
I am asking this because we have a lot VBR installatsion and we use Powershell to keep track on VBR versions, but this needs to be defined and written in scripts.
12.1.1.X if 12.1.1.56 is found to contain a critical issue and we need to replace it with a fixed version.
12.1.2.X if business as usual, when we ship periodic maintenance releases every 3 months on average.
12.2.0.X if we decide to skip the previously mentioned update and go for a minor release instead, as to deliver a few particular features sooner.
13.0.0.X if we don't do any of the above and go straight for the next major release.
Where X is a build number.
All is hypothetical of course, just to show the logic behind the build numbering.
