Drop CHANGELOG.md and switch to github releases

[tiedotguy]

Currently changes are tracked in [CHANGELOG.md], including the version, which is a bit of a pain to manage if there's more than 1 thing going on at a time due to merge conflicts on a non-critical file.

Historically I've cleaned this up by just pushing to master, however that's not an option anymore. As such, I propose dropping it (marking it as deprecated but leaving it for historical value) entirely and switching to github releases. This would be done after #264

Personally I'm not a big fan of having the history tied to the github ecosystem rather than the repo, but I value the productivity more.

[tiedotguy]

opinions, @ash2k, @aelse ?

[ash2k]

👍

[aelse]

Doesn't a merge from master into a branch before raising a PR solve this? We're not so fast moving that changelog gets frequent updates.

[tiedotguy]

It does, but it effectively serializes the PR process, and #260 is up to 3 merges now.

[aelse]

If we switch to github releases it makes this project more of a snowflake concern for us to manage and I want to avoid that. It doesn't seem like it's a huge burden to resolve conflicts in a markdown file, even if it happens 2 or 3 times in the course of a long running PR.

If we can do better on reducing the time it takes to get changes merged in this problem probably goes away for the most part. Not all of us are paid to work on this project (any more, @tiedotguy 😄) and any time given is a gift, but I'll put more focus on giving timely feedback in future

[MovieStoreGuy]

I think it is fair enough to say that we carry on with using the change log and using tagged commits @tiedotguy