Update Minor versioning policy to make sure we do a minor version bump even when there are new feature added , this is done to let customers know that a new feature is released (#5583)

Author: joviegas

VERSIONING.md

@@ -3,7 +3,7 @@
 The AWS SDK for Java v2 uses a versioning scheme that follows the format: `MAJOR.MINOR.PATCH[-QUALIFIER]`. Revisions to different version components communicate the risk associated with changes when upgrading to newer versions of the SDK:
 
 * `MAJOR` - Huge changes, expect API incompatibilities and other breaking changes.
-* `MINOR` - Medium risk changes. Upgrading SHOULD usually just work but check the [release notes](CHANGELOG.md). Example changes might include incrementing minimum Java version, deprecating APIs, or significant changes to core runtime components. Changes to `MINOR` version MAY contain backwards incompatible changes under certain scenarios.
+* `MINOR` - Medium risk changes. Upgrading SHOULD usually just work, but check the [release notes](CHANGELOG.md). Example changes might include incrementing the minimum Java version, deprecating APIs, significant changes to core runtime components, or introducing new major features such as the transfer manager or S3 multipart client. Changes to the `MINOR` version MAY contain backward-incompatible changes in certain scenarios.
 * `PATCH` - Zero to low risk changes. New features and bug fixes that should be safe to consume without much worry.
 * `QUALIFIER` - (Optional) Additional release version qualifier (e.g. PREVIEW). Most releases are not expected to have a qualifier.