We really need to do something about the release process of this library!
There is way too much manual work required to create a release. That is why canches bulk up and then releases even get harder to do.
Let's think about what we can improve..
I'll take care of pluging in Travis CI
We could automate the changelog generation process similar to the angularjs team. They have restrictions for their commit messages (reference). You can then check whether the commit message meets the criteria with Travis by running a script like this. Even better if we use a git commit hook that checks the message before the commit.
This allows us to generate the changelog automatically. See here. The result looks like this. What do you think?
Edit: I just realized that the git changelog procedure is already described in the first post, sry.