2.2.0: change in tagging convention? 🤔 about gmpy HOT 8 OPEN

It was a mistake. What is the best option? Create a new tag with dots and leave both tags, or create the new tag and delete the old one (trying to do a rename)?

from gmpy.

Best to be hones would be just <version.with.dots> or v<version.with.dots> because in autogenerated tar ball base directory is automatically generated out of <repo-name>-<git-tag> and if in tag is used on the begging v it is skipped (to make easier branching with <version.with.dots> on v<version.with.dots> to branch some version + some critical changes).

from gmpy.

Is it okay to just create a tag 2.2.0 and leave the old tag as-is? There haven't been any code changes.

from gmpy.

Perhaps, it might be a good idea to automate release process. In the diofant project I just do git push origin v1.2.3, that's all.

from gmpy.

You can peak as well on automating procedure of creating GH release entry
RDFLib/rdflib-sqlalchemy#95
RDFLib/rdflib#2036
click-contrib/sphinx-click@abc31069
frostming/unearth#14
jaraco/cssutils#21
latchset/jwcrypto#289
latchset/jwcrypto#289
pypa/distlib@98b9b89f
pywbem/pywbem#2895
sissaschool/elementpath@bf869d9e
sissaschool/xmlschema@42ea98f2
sqlalchemy/sqlalchemy@5e88e6e8

from gmpy.

BTW, I'm not sure, that @casevh has required permissions for this repository...

from gmpy.

I have tagged v2.2.1 and released on PyPi.

from gmpy.

Probably, this can be closed?

from gmpy.