AFAIK, SQL Anywhere versions have always used a three-part version number - e.g. versions "5.5.05", "8.0.3", "12.0.1" and so on - and the build number as forth component, such as 184.108.40.20617.
AFAIK, with the exception of version 5, where there were both 5.0.x and 5.5.x releases, the second part of the version number has always been a zero - which has sometimes irritated new users, as they think of using SQL Anywhere 11.1 or 12.1, which do not really exist as versions...
With SQL Anywhere 16, it seems the "superfluous zero" has been dropped officially from the version number, as can be seen in the DCX homepage:
So I'd expect the next MR to be called 16.1 instead of 16.0.1...
Question: Is that observation correct?
Build numbers are still using 4-part notation, i.e. the 16 GA is 220.127.116.114. - And no, I don't claim this the most important change in v16:)
Volker, you are very observant.
As part of the merger with SAP we have adopted the SAP numbering scheme for version releases and hence the externally visible version number "16.0" instead of our usual "16.0.0". Note that internally we are continuing to use the four part numbering scheme "18.104.22.1684" (i.e. major.minor.0.buildnumber). Currently the plan is that the third internal number will always be zero.
If and/or when we do a maintenance release of version 16 the version number would most likely be 16.1 but this is a forward looking statement and is subject to future circumstantial changes so please do not make any critical decisions (financial or otherwise) based on this statement! :-)