Add change log

[psq]

First shot included here: 1bcf600

If I missed something, misrepresented something, or mis-attributed, please comment here, or create a PR.

Will close in a few days.

[mrjoelkemp]

+1 to this. It's more overhead, but essential to give transparency to what's happening in a release.

We could generate a release on github.com, generate release notes via the shell: git fetch upstream && git log 0.4.1..0.4.2 --merges --pretty=%s%n%b%n

This assumes that you have a remote named upstream if you've forked the jsdox repo. If you're generating release notes from the main repo, replace upstream with origin.

@psq You'll need to do a git push --tags on your local machine each time you npm publish. Publishing automatically creates a git tag with the version number. Can you do a git push --tags (don't create a new npm version, just push existing tags up) as soon as you can?

[psq]

@mrjoelkemp this assumes I was not bumping the version manually :( there are no tags, but it should be easy to regenerate the recent ones. Will do.

[psq]

alright, created tags for versions all the way down to v0.3.0 (except v0.3.1). Will use npm version from now on to do this automatically :)

[mrjoelkemp]

Great job! Thanks for taking care of it.
On Sep 4, 2014 6:11 PM, "Pascal" [email protected] wrote:

alright, created tags for versions all the way down to v0.3.0 (except
v0.3.1). Will use npm version from now on to do this automatically :)

—
Reply to this email directly or view it on GitHub
#66 (comment).