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.
Would that be ok?
Do you plan to only upload release candidates as dev releases, or more frequent? I'd be fine with the former, but I don't like if PyPI is spammed with dev releases. I mean devpi was created for this exact use case. And I don't see much difference in installing with "pip --pre" versus "pip -i ..." on a CI. Regards, Florian Schulze