Release a new version on PyPI with the latest changes and define how to trigger new version releases in the future

[Grim-bot]

Many fixes and improvements have been made to the repo since the last version release on PyPI (version 0.0.7, June 2020). For instance, software security issues detected by dependabot have been fixed. Once PR #17 is accepted and merged, we should release a new version.

In anticipation of future fixes and improvements, we need to decide how, when, and by whom new version releases on PyPI can be requested.

[Grim-bot]

Are the current unit tests sufficient to ensure that the new version can be successfully installed by users ?

[Grim-bot]

We can also split this into 2 separate issues.

[tristantreb]

1. Released 0.1.0 on PyPI

2. About PyPI releases:
   Who should do them? The reviewer of the last pull request (I'll do that one)
   How must it be done? See details in CONTRIBUTING.rst under Push releases to PyPI

3. Moving tests questions to new issue Define process to validate code prior to release #20