Design and implement release management process about pydriverr HOT 1 CLOSED

First of all: Decision about a release depends on us and this means not every commit triggers the release process

So I suggest following process and tools that we should create:

Locally:

Run in the repo tool release 0.0.1 that will:

1. Create branch release/v[release_number] i.e. git branch -b release/v.0.0.1 - we use semantic versioning
2. will run poetry to bump version in the pyproject.toml: poetry version 0.0.1
3. will generate the changelog using: https://pypi.org/project/gitchangelog/
4. will add changed files to changelist and perform commit: release: Create v.0.0.1 release
5. will create annotated tag with version: git tag -a v0.0.1 -m "Release v1.0.0"
6. will push everything to remote branch

Remotely:

1. Manually open PR for created branch release/v.0.0.1 for merging into master branch
2. Devs perform the review and when everything is OK we merge the PR -> proceed to Actions step (merged branch is deleted).
   • If something is wrong corrective actions needs to be performed and pushed with force to review
   • If one decides to not release this he has to: delete release/v[version] branch

Actions:

1. When actions on the release branch will be run it will be based on the SV job, so it will build wheel and test the app
2. Resulting output from SV (built wheel) will be put on the Release in Github and ...
3. ... will push the package and changelog to pypi by calling poetry publish -u $PYPI_USERNAME -p $PYPI_PASSWORD -n

Note: in order to publish register on pypi

@pajhiwo what do you think?

from pydriverr.