Release v0.9.0 #480
Merged
Release v0.9.0 #480
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
Much less confusing... Signed-off-by: beorn7 <beorn@soundcloud.com>
stuartnelson3
approved these changes
Oct 15, 2018
no objections. |
This ends a long time of not really tagging versions (as it didn't make a lot of sense - we could have tagged every commit with a new minor release essentially). I still worked through the git log and GH issues to create a nice CHANGELOG.md. As dependency management tools really love version tags these days, I plan to tag more often from now on. The ideas behind the pre-1.0 version numbers are explained in the README.md as changed in this commit. I also changed the issue template accordingly. Signed-off-by: beorn7 <beorn@soundcloud.com>
beorn7
force-pushed
the
beorn7/release
branch
from
920b9da to
b2c0ab4
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
@grobie @stuartnelson3 let's finally do this! I'll tag once this is merged.
@krasi-georgiev Since the API client is completely independent from the instrumentation library, but both are in one repo, we will share the tagging. I thus also tried to put API client changes into the CHANGELOG.md. Hope that works for you.
This ends a long time of not really tagging versions (as it didn't
make a lot of sense - we could have tagged every commit with a new
minor release essentially). I still worked through the git log and GH
issues to create a nice CHANGELOG.md.
As dependency management tools really love version tags these days, I
plan to tag more often from now on. The ideas behind the pre-1.0
version numbers are explained in the README.md as changed in this
commit.
I also changed the issue template accordingly.