v0.2.0 #211
Closed
v0.2.0 #211
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
|
@ericchiang thanks for writing these notes up, but we use GitHub releases and git tags to manage our release process. When we are ready to cut the release, we will cut a signed tag and use your changelog as the start of the release notes. |
|
@bcwaldon thanks. Realize now this PR should probably just be "added changelog". Was planning on doing a proper github release once this got in 😄 |
|
@ericchiang We use the GitHub release history as the de facto changelog, so I don't think this is necessary. |
|
@bcwaldon ah, okay. |
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.
Would like to get #202 and #210 merged before releasing. Also probably need to change some of the build scripts to use a version rather than a git SHA.
Is there anything else we want to wait for?