Change ODBC version to 1.4 for release

[joshuali925]

Signed-off-by: Joshua Li [email protected]

Description

Driver versions are independent of core and plugin versions. Since there are no breaking change after ODBC 1.3, releasing it as version 1.4.0.

Issues Resolved

[List any issues this PR will resolve]

Check List

• New functionality includes testing.
  • All tests pass, including unit test, integration test and doctest
• New functionality has been documented.
  • New functionality has javadoc added
  • New functionality has user manual doc added
• Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[penghuo]

I think we are following semvar. Totally agree we should not bump major version if there is no breaking change.
Questions?

1. How does customer aware of the relationship between SQL and ODBC driver?

[joshuali925]

I think we are following semvar. Totally agree we should not bump major version if there is no breaking change. Questions?

1. How does customer aware of the relationship between SQL and ODBC driver?

ODBC driver tries to be backwards compatible, even with ODFE SQL, so right now users can mix ODBC >= 1.0 with different SQL versions.

When there is a breaking change, ODBC will do a new release (2.0) and indicate it's no longer compatible with SQL less than a specific version. and when it happens we can probably include a version compatible matrix in readme