Add a CHANGELOG file

[tcharding]

Add a CHANGELOG file including release notes for the current version (minor and point) as well as an "unrleased" section for the upcoming release.

cc benma

Close #83

[apoelstra]

utACK faa5229

Looks good to me. I don't understand the "woops" comment. What kind of release would you have us release non-breaking changes in?

[clarkmoody]

ACK faa5229

[benma]

utACK faa5229

Looks good to me. I don't understand the "woops" comment. What kind of release would you have us release non-breaking changes in?

Afaik according to semver, in 0.y.z anything goes. Beyond 1.0.0, non-breaking changes that add functionality should bump the minor version.

You could consider going to 1.0.0 soon as the package is in use in production.

[tcharding]

Thanks @benma, I thought pre-1.0.0 we still were supposed to do a minor release (which is major because pre-1.0.0), the woops was because we did it in a patch release.

You could consider going to 1.0.0 soon as the package is in use in production.

That is top priority across the whole rust-bitcoin org at the moment. Specifically we are focusing on crate smashing to try and reduce the size of the crates to hasten the 1.0 release - no excuse for rust-bech32 though, we just have to get our shit together.