Use scm setuptools for auto-versionning

[Pierre-Sassoulas]

Description

Move to scm_setuptools for easier release. Update the release doc.

Type of Changes

	Type
✓	✨ New feature
✓	🔨 Refactoring
✓	📜 Docs

Related Issue

#4399 #4400

[cdce8p]

Tbh I'm not too familiar with setuptools_scm. If you think it will make things easier, go for it.

[Pierre-Sassoulas]

Basically it removes the need to change the version and is based on tags only. So no more change to do in the version value before and after release.

[wj-Mcat]

Wating for this pr to be merged so my github ci can pass 👻

[Pierre-Sassoulas]

I don't understand @wj-Mcat ? Why would it fix your CI ?

[Pierre-Sassoulas]

@cdce8p I think we can do that in 2.8 directly and we don't have to change the tags either, scm_setuptools seems to understand the tag.

[cdce8p]

@cdce8p I think we can do that in 2.8 directly and we don't have to change the tags either, scm_setuptools seems to understand the tag.

Not exactly sure what you mean here. In my experience the tag is usually just something like v1.x.x, but if the current naming schema works there is no reason to change it.

[Pierre-Sassoulas]

Not exactly sure what you mean here.

I wanted to change the tag from pylint-1.2.3 to v1.2.3 but the generated version by setuptool_scm is 1.2.3 for both. So we can keep the standard. We might still want to change the tag to something standard for pre-commit the version will still be pylint-1.2.3 in .pre-commitconf.yml...

[cdce8p]

Not exactly sure what you mean here.

I wanted to change the tag from pylint-1.2.3 to v1.2.3 but the generated version by setuptool_scm is 1.2.3 for both. So we can keep the standard. We might still want to change the tag to something standard for pre-commit the version will still be pylint-1.2.3 in .pre-commitconf.yml...

Ah, I see. I would recommend to use v1.2.3 then.

[cdce8p]

Only if you what to change the tag schema

[wj-Mcat]

I don't understand @wj-Mcat ? Why would it fix your CI ?

I use pylint to test my project, but it occured error when install new version of pylint.

So, I'm waiting for this pr to be merged.

[Pierre-Sassoulas]

Ho okay, it's actually another problem fixed in #4407 but I'm going to release 2.8.2 just after merging this one (that just speed thing up for us maintainers) so you're still right :)