OCI Go SDK change of versioning schema

[ZiyaoQiao]

On/after April 12, 2022, OCI Go SDK will adapt a new versioning schema.

• The breaking changes in service client APIs will no longer result in a major version bump (x+1.y.z relative to the last published version). Instead, we will bump the minor version of the SDK (x.y+1.z relative to the last published version).
• If there are no breaking changes in a release, we will bump the patch version of the SDK (x.y.z+1 relative to the last published version).
• We will continue to announce any breaking changes in a new version under the Breaking Changes section in the release changelog and on the Github release page [https://github.com/oracle/oci-go-sdk/releases].
• However, breaking changes in the SDK's common module will continue to result in a major version bump (x+1.y.z relative to the last published version). That said, we'll continue to maintain backward compatibility as much as possible to minimize the effort involved in upgrading the SDK version used by your code.

We're currently investigating converting OCI services exposed in the SDKs into standalone sub-modules to make the dependencies more manageable. Please let us know if you have any questions or concerns regarding this version schema change. Thanks.

[ZiyaoQiao]

Today we release OCI Go SDK v65.1.0 using this new schema - https://github.com/oracle/oci-go-sdk/releases/tag/v65.1.0 The breaking changes in this version are resulting in a minor version bump (x.y+1.z relative to the last published version) instead of a major version bump (x+1.y.z relative to the last published version). Please let us know if you have any questions or concerns. Thanks!