automate release process

[ms-lolo]

when we decide to create a new non-dev release of our wheels, what do we need to do right now (already automated or not)?

• calculate version number
• validate packages
• update change log
• create git tag
• publish artifacts

i want to create commands in rats-devtools to run this process so we can test everything without github actions. then we can pick which of these commands are run with github actions.

[ms-lolo]

@jzazo any high level steps i missed?

[jzazo]

• Calculate version number and bump the pyproject versions.

The reason of bumping is in my opinion not to install non-matching versions of packages incompatible between them.

I think all of the above can be achieved with commitizen. It can be ok if you want to wrap it up with a devtool command, but I don't see the benefit. We can discuss it some time.

[ms-lolo]

@jzazo, regardless of implementation details, i want to define the needed capabilities. do we expect each version in pypi to match a git tag in this repo? do we expect dev# releases in pypi to match a tag? do all pypi wheels need to come from the main branch?