In the light of the current problems with metadata in 3.3 and in the interest of making the releases even easier, I would like for us to move to a "publish on tag" method which we have been applying successfully in a number of pytest plugins (notably pytest-xdist).

I propose to change our release process to:

1. Manually use our invoke tasks to run regendocs, changelog and push a PR with the changed contents (very similar to what we do today).
2. After the PR is approved, we push a tag and Travis publishes the package automatically.

Notably missing from the current approach is using devpi and testing the package manually (I have been using devpi-cloud-tester); I think today the tools are mature enough where this step is not necessary, plus we already test using tox, which ensures the package is working properly.

Further @jaraco and a few others use this approach successfully, which gives me further confidence.

This is not fully automated yet, but I believe is a step in that direction nonetheless.