Bump version for development version

[blueyed]

version is defined explicitly in setup.py (https://github.com/typeddjango/django-stubs/blob/2ef7ff33091316d02f51950cbfccc12ba434afb8/setup.py#L35).

This causes compatibility issues when using pip install -e … for local development, but wanting to revert to the pinned version (pip install django-stubs==1.10.1), and pip considering the constraint to be satisfied still.

I am not sure how to address this best, but if e.g. setuptools-scm or https://github.com/codrsquad/setupmeta would be used to have the Git version in the version number it would solve this problem. But also just bumping it in the Git main branch already could help, possibly using a .devX suffix then to not cause issues with the actual release then.

This is a minor issue, and feel free to not add overhead for this, but wanted to mention it still, since it is not the first time that I was confused by this (when ignore comments were not needed locally anymore, but on CI still).

[sobolevn]

I am +1 for automating this, since I usually forget about -dev prefix when doing a version bump.

We can add a script for it here: https://github.com/typeddjango/django-stubs/blob/master/release.sh

PR is welcome!