Hi all,
495 is merged and I replaced the version on devpi. I think we can release it in the next few days.
I already realize that there is much room for improvement how I go about this to make it easier and cleared, but I am learning as I go along hopefully.
For the next release, I suggest going back to using dev versions (this will be automatic when setuptools_scm is merged) and always pushing one or two dev versions to pypi before an actual release. This makes it easy to decide in which CI chain I like to be adventurous
and always use the tox dev versions by default by installing tox with
`pip install --pre tox` instead of having to point it at a special dev index (that might change, if somebody else prepares a release from their dev index).
I will
integrate using the --pre versions of tox into our CI at work then, so
that I don't even have to think about it anymore.
My goal is to reduce the effort of making releases while still having a
decent level of exposure of dev versions to real world applications in an as automatic as possible manner. If a handful of people activate that in their company CI configurations, travis.yml ... wherever, we might catch a few bugs before a release without having do too much manual coordination.