Bump to version 2.0.0 in main. #824
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I think I'll likely abandon #823 in favor of submitting in the main branch first and then cherry-picking the change over to the releases/2.0 branch. |
SparkingSpork
approved these changes
Jan 11, 2023
reckenro
commented
Jan 11, 2023
dmondrik
approved these changes
Jan 11, 2023
astarche
approved these changes
Jan 11, 2023
harsha-bhushan
approved these changes
Jan 12, 2023
reckenro
added a commit
to reckenro/grpc-device
that referenced
this pull request
Jan 12, 2023
reckenro
added a commit
that referenced
this pull request
Jan 12, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does this Pull Request accomplish?
Bumps the executable version from 1.5.2 to 2.0.0 in the main branch.
Why should this Pull Request be merged?
We should mirror what RTOS does for releases. When we start development on the next release, update the version in main. Then when when we create the releases branch for it it will have the correct version. Then post-release, update the main branch to the upcoming release.
What testing has been done?
Relying on the build.