Document release process?

[ericdill]

Anyone know fully how we do releases here? I'm specifically looking to understand steps 4 and 5.

1. Make empty commit: `git commit -m "Tagging " --allow-empty
2. Add tag: git tag -a -> then describe release in editor
3. Push changes to master
4. Release on pypi?
5. Update conda-forge recipe?

cc @ocefpaf @CJ-Wright

[CJ-Wright]

Do you want to use rever to run the releases?

[CJ-Wright]

(for some context this is how conda-build runs their releases)
(CC: @scopatz)

[ocefpaf]

Step 4 could be automate in Travis or as a GH Action. I can send a PR later today. Step 5 I would just leave it to the bot.

[ericdill]

sounds like you both have solid ideas. I don't really have a strong preference either way. Seems like a "do-ocracy" will win here :) My only ask is that can whomever takes over the release instructions documents it in the readme?

[CJ-Wright]

Just as an update I implemented rever I just need to add it to the readme.

[ocefpaf]

@ericdill with #77 all we need to do is to issue a tag/release on GH. The PyPI release is automated and the bot will pick that one up. I usually create the release using the GH interface b/c that is easy and we now have the automated changelog feature. Two clicks and we are done!