CHANGELOG cleanup

[husio]

I have manually edited and rewritten latest entries in the CHANGELOG
file. I have removed all points that were implementation specific (ie
tests) and are not important for the users.
I was trying to keep only information that is improtatnt for our users,
without going too much into implementation details.

[webmaster128]

:)

[ethanfrey]

I like this version.

Except some things were erroneously moved from 0.15 to 0.14

[ethanfrey]

Also missing:

• Adjustments to escrow processing (timeout inclusive)
• Added validator-subjective anti-spam fee

I do kind of like having a section "improvements" to mark some of the details there, like the overhaul of the testing framework. Even if it doesn't change the API it does document many days of work

[husio]

I understand that we want to show what we worked on because we are proud of the results. Is it really helpful for the readers though? Is it helpful for @webmaster128 (our only user that I know of 😆)

[husio]

@ethanfrey I am a bit confused by the timing. I am using d6acfb0 as the version bump commit. Which one should I use instead? I should have used GitHub interface for this instead v0.14.0...master because we are tagging a random commit as the release 😢 3c1504e

[husio]

Should be all good now. @ethanfrey please have a look once more.

I have created #631 because I believe this will be a recurring problem and it really sux to edit the CHANGELOG after the fact.

[ruseinov]

This looks much better, thanks!

LGTM, I suppose Ethan needs to have another go at this as he seems informed about what goes where.

[ruseinov]

@ethanfrey ^^ can you have a go at this so that we can merge and release? Thanks!

[ruseinov]

@husio btw let's aim this at master directly and close the other PR that I've opened, I don't think it's necessary to merge one into another etc.

[ethanfrey]

Looks very nice.
And I think the idea of adding checks to the CI is a great way for us to train ourselves to remember. Just like clicking that little project button on PRs....