Discussion: Upgrade repo version after a release to dev to not match release version

[Daraan]

A while ago to do some tests I wanted to upgrade my current typing_extensions version to the current GitHub version by using
pip install git+https://github.com/python/typing_extensions.git.

I also blame pip here because it does not tell that it doesn't install anything. pip did not perform an upgrade because the current release, which I had already installed, has the same version as the GitHub repo (4.12.2).
Only after a while I realized that nothing was upgraded and I had to use --force-reinstall to do it.

I want to discuss if in the future, after some merged PRs, the version of the GitHub repo should be upgraded to a +1dev to not be equivalent to the latest release version.

[JelleZijlstra]

Sounds good. We can update the release instructions in the repo to mention this.