Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR simplifies the SDK release process by reducing the number of release branches, naming conventions, and number of steps to release:
main
branch. Developers should still create a release branch, but only to bump the version number and merge tomain
. The previous release process required tagging releases from release branches, and making multiple updates to the release version number both before and after tagging the release.CHANGES.txt
. Developers should maintain the changelog via the GitHub tag/release UI, which serves as the source of truth for version numbers and provides a 'description' box for changes. The previous process of tracking the changelog required duplicating the same information in bothCHANGES.txt
and the tag/release UI.maint-1.0.0
and1.0.0dev
.This MR doesn't make any changes to automated CI workflows used in the release process; the changes proposed here should not have any side effects with existing CI workflows.
Upon review and acceptance, I will also make some changes to the wording in the PR template which still includes references to the changelog: