-
Notifications
You must be signed in to change notification settings - Fork 32
0.2.0 release #36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
0.2.0 release #36
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This all looks good to me; I just had one question.
Before we release 0.2, it would be good to merge #37 and #38 because they're breaking changes. (Note that if we merge #38, we should add to the release notes in the README that the extension traits can no longer be implemented in other crates.) I've also created #40, but it can wait until 0.2.1 if needed.
I merged all of them - things we already discussed and agreed upon.
I have added a note on extension traits to the changelog, as you suggested.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I rearranged the changelog slightly. Everything looks good to me. I think we're ready to release once this is merged!
Would you like to do the release, or would you like me to handle it?
Let me try, let's see if I can get it right 😛
@LukeMathWalker Thanks for doing the release. Will you please add a 0.2.0 tag to the commit in Git and push the tag to GitHub?
Done! (although directly from GitHub GUI)
Getting ready for releasing - I have added a new entry to the changelog, updated dependencies where needed and put some more info on the README.md.
Are we ready to go? What do you think @jturner314?