Document release process

[letmaik]

trafficstars

I think this is roughly:

1. Ensure version is set to the next SemVer version in setup.cfg
2. Create a new GitHub release with git tag v<x>.<y>.<z>, e.g., v1.2.3
3. Wait for CI to run for the new git tag
4. Make sure that CI ran successfully and pushed the package to PyPI

[TimothyClaeys]

One other thing I can think off is to make sure that the documentation is up to date and verify if it is successfully deployed to pycose.readthedocs.io.

[letmaik]

Good point, it says "latest" on the docs, shouldn't it include the version? Otherwise it becomes a little hard to check.

EDIT: The problem is not "latest", but rather that the individual versions are not listed. Example: https://msticpy.readthedocs.io/en/latest/ This also uses a v prefix for the git tags (same as pycose), which I first thought was the issue here. Not sure why this happens.