Change to no-guess-dev versioning

[FlorianWilhelm]

@abravalheri, was there a reason we had post-version in this extension?

[abravalheri]

Thank you very much @FlorianWilhelm for spotting this!

If I remember correctly when we were migrating from v3 to v4, there was a short period of time that no-guess-dev was not an allowed value (?), so I ended up using post-version during the transition...

By the way, is setuptools-scm still recommending not to use no-guess-dev?

[abravalheri]

The CI seems to be a bit confused, but everything should be fine if we run it again...

[FlorianWilhelm]

The recommendation is still not to use no-guess-dev as it brings no smart version guessing. @RonnyPfannschmidt and I agreed that the other version schemes are much better if you are a professional software developer working on a professionally set up project with release and git workflows. On the other hand, we also agreed on the fact that users of PyScaffold might be overwhelmed with what you need to do in the sense of git workflows to really benefit from setuptools-scm's smarter version schemes. For this reason we stick to no-guess-dev but mention in the template that there are smarter version schemes to check out. I already pushed a commit with this change to PyScaffold between the years.

[abravalheri]

Thank you very much for the clarification!

[RonnyPfannschmidt]

Reminds me, i need to release a breaking version of setuptools_scm that makes no guess dev smarter