Resolve "Create a release using CI/CD"

Closes #17 (closed)

List of changes:

• .gitlab-ci.yml: Before_script is only executed for the tests/linters jobs. They are in the same stage. A new stage (release) is added that is triggered by tagging. The Build job will deploy the package to the Package Registry. The Release job releases the code.
• pyproject.toml: A toml file is added to automatically build the package and write the __version__.py, based on git tagging (using the setuptools_scm module)
• setup.py: the version is removed here
• __init__.py: the version is retrieved here, from the automatically generated __version__.py

\approve @ds @gislars

assigned to @laurens

added 1 commit

• c412cf69 - Add build and release jobs to create version packages

Compare with previous version

added 1 commit

• 4c7cece7 - Support automatic builds and releases using Semantic Versioning

Compare with previous version

marked this merge request as ready

added 1 commit

• 8efdbece - Add later black version

Compare with previous version

added 1 commit

• 87f3faa2 - Add __version__ to .gitignore

Compare with previous version

added 1 commit

• 520b3b49 - Support automatic builds and releases using Semantic Versioning

Compare with previous version

assigned to @gislars and unassigned @laurens

changed the description

I would like to have some documentation about it.

• how to create a release
• steps are necessary before/after a release
• what settings/files needs to be modified
• description of the files (like the overview in this MR)

I guess this could be added to collaboration instead of having it in every repo.

assigned to @laurens and unassigned @gislars

approved this merge request

assigned to @gislars and unassigned @laurens

resolved all threads

assigned to @laurens and unassigned @gislars

approved this merge request

merged