Target API version 510 by default

[KrzysFR]

The current default API version is 300, which correspond to the v3.x of FoundationDB. The latest version available is now v5.1.5, which add some features compare to the old v3.x (more atomic operation types, and versionstamp).

Since not a lot of people are probably using the .NET binding in production, and since probably most people would jump straight to v5.1, I think that it is reasonable to target API version 510 by default.

This means that application that do not explicitly request an API version, or call Fdb.Start() without arguments, would now default to the latest API v500. It is unknown at this time if there has been changes to the behavior of existing commands between 300 and 510.

Looking at other binding (java, python, etc...) it appears that some have dropped support for pre-510 versions.

[ajbeamon]

Our latest released API version as of 5.1 is 510. We did drop support for older API versions in some bindings because of breaking changes to the APIs, but where possible we've tried to continue supporting for older versions.

[KrzysFR]

Since I have the luxury to not have to support older API versions, I can simply target 510 by default, and add support for all the new APIs. We'll see how to handle API versioning in the next round of updates.

[KrzysFR]

This has been changed in 80f4312 to API version 510 by default. I'm tracking a few regressions which seem to date back from API 300 so probably pre-existing issues.