Please add a ChangeLog file

[marshallpierce]

Please add a ChangeLog file

[Emerentius]

Ah, sorry, I missed that. I ran cargo upgrade for a project and went through all dependencies where this resulted in a major change and for most projects this was called Changelog either as a separate file or in the README.

Those notes are good, however you can't quickly tell what is a breaking change and what isn't. I would suggest specifically marking those changes.

[seanmonstar]

Alternatively, tag releases here: https://github.com/alicemaz/rust-base64/releases

[marshallpierce]

This is one of my least favorite aspects of Cargo -- it doesn't leave a VCS trail of when a release was actually performed to crates.io. I think a human-oriented changelog file would be nice, though.

[alicemaz]

I've been meaning to do this for awhile, can probably reconstruct one retroactive from the start. tagging releases would also be nice for if/when fixes have to backported, recently had to do this relying on Cargo.toml rev history. I'm in the middle of a cross-country move presently, will probably have time next week

[marshallpierce]

I pushed version tags.

[marshallpierce]

I think this is good now; re-open if the recently merged release notes aren't satisfactory.

[Emerentius]

Tags are not a solution to this at all. There is no info on what the changes are between versions. Presumably there were breaking changes between 0.12 and 0.13, how could a dependant of this library possibly find out without sifting through the commit log?

[marshallpierce]

If https://github.com/marshallpierce/rust-base64/blob/master/RELEASE-NOTES.md isn't satisfactory you're entitled to a full refund.