Versioning Strategy

[aajtodd]

Create and document a versioning strategy for aws-sdk-kotlin, smithy-kotlin, and aws-crt-kotlin.

The Java SDK for instance versions everything together regardless of what changed. e.g. a change in one model will bump versions of the runtime and all other generated clients. This makes the most sense to me as it allows customers to set a single version and know that it all works together. It also is less burden on maintainers to know what versions work with what. The only caveat is this requires really good release notes so that customers can understand what actually changed and if they should care about upgrading or not.

The repo split makes this more interesting as coordinating releases and published artifacts will be harder. Perhaps the crt bindings and smithy-kotlin will get their own versioning and aws-sdk-kotlin will be versioned as one. Needs some thought and consideration.

[github-actions[bot]]

This is a very old issue that is probably not getting as much attention as it deserves. We encourage you to check if this is still an issue in the latest release and if you find that this is still a problem, please feel free to provide a comment or open a new issue.

[github-actions[bot]]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see. If you need more assistance, please either tag a team member or open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.