0.2.0 release - #36
Conversation
There was a problem hiding this comment.
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. |
jturner314
left a comment
jturner314
left a comment
There was a problem hiding this comment.
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 |
|
Done! (although directly from GitHub GUI) |
2 participants
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?