I started thinking along those lines while preparing the release, but wanted to get the first release out old skool like Holger sketched out for me. I did already set up vagrant boxes for (arch)linux and Windows(10) with all interpreters installed which would add portable dev and test envs to the project. I did not add the Vagrantfile to the project yet, because I wanted to hear first, if this is considered a good idea. I like having a Vagrantfile in a project for tests and to help others getting started quickly, but it obviously has not only upsides and carries a (in my view small, one it's set up) maintenance burden.

@Bruno that's very cool indeed, I will have a closer look at that as soon as I can and add it to our CI.

Preparing a release is should be basically preparation free in my ideal world, so that every successfull built can be released right away without any extra testing necessary.

I was also wondering if there is something speaking against introducing Ronnies https://github.com/pypa/setuptools_scm for tag based versioning? Love that tool - one less thing to worry about, just tag the thing and off you go :)

Cheers