Add a release checklist

[chatcannon]

I just messed up the 0.4.0 release by forgetting to update the version in setup.py before tagging the release, and I have done it before. If I want @ml-evs to be able to make releases too, then it is even more important to document the process properly.

[ml-evs]

I find the combo of setuptools-scm and releasing directly from GH actions works very well, happy to set it up if you like (would then only need your PyPI token added as a secret for this repo, plus careful handling of who can make GitHub releases). Thanks for doing 0.4.1 anyway!

[chatcannon]

I had a look at the setuptools-scm documentation. It looks like the tooling has got a lot better since I last set up a Python package.

However, given the mess of git-lfs bandwidth limits I don't want to depend on GitHub actions for anything right now.

[ml-evs]

I had a look at the setuptools-scm documentation. It looks like the tooling has got a lot better since I last set up a Python package.

However, given the mess of git-lfs bandwidth limits I don't want to depend on GitHub actions for anything right now.

Hi @chatcannon, just to point out we don't rely on git-lfs as much anymore since my hack in #118. It would be very helpful for other maintainers to be able to make releases rather than pinning to specific git versions in our own projects. I'm still happy to set up the above if you like (otherwise we are probably due a release now)