Update changelogs for 0.2a0 release #253
Merged
Conversation
This file contains hidden or 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
lzchen
approved these changes
Oct 29, 2019
toumorokoshi
approved these changes
Oct 30, 2019
c24t
added a commit
that referenced
this pull request
Oct 30, 2019
c24t
added a commit
that referenced
this pull request
Oct 30, 2019
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.
Follow-up to #251. See also #250, though ideally we'd have merged this PR before that one.
We have to choose whether to update the changelogs before or after release. One benefit of changing them on master before the release is that we can split off the release branch after updating them, but before updating the version number. After the split the release branch should get the next release version (here
0.2a0) and the master branch should get the next dev version (here0.3.dev0).This matches the OpenCensus release strategy with one important exception: here all
extpackages get the same version, even if they haven't been updated since the last release. This is why the newext-jaegerandext-opencensus-shimpackages start at version0.2a0.