Track release notes in this repo

[alaric-dotmesh]

As developers, we'd like our release notes tracked in version control, along with the versions they pertain to, so we can have a better understanding of (and ability to search...) the history of our product.

To do this, we could have a RELEASE.md file with headings for each release, and put the release notes in there. We can add to the top of the file as we develop stuff, and then we can then further automate the release process to feed the latest release's notes into Github and to add a heading for the actual release number we chose at the top of the file, thereby closing off the additions for that release.

[alaric-dotmesh]

Release 0.5.2 took ~45 minutes; a lot of that was due to having to poke at test flakes to get it passing, but it would be good to look more at manual steps in the release and automate them further.

[Godley]

Thoughts on autogenerating the release notes + release itself: Github allows you to do releases via git tag - we could have a script which:

• does a diff against the release branch, pulling out all issue numbers beginning with # and then selecting the unique ones
• talks to the github api and gets the title for the issue number - we could also just take the first title of the first commit for that issue, but it's not always the same + likely to be "I just did this bit"
• creates the tag via git tag then does git push --tags to release
• creates a commit on master branch to update the file described above

There might also be some open source tool we can use to generate the changelog - previously used gitchangelog and other cli tools which pull out specific commits based on a regex.

[Godley]

This is moderately interesting - https://github.com/toolmantim/release-drafter/blob/master/README.md