[x] Increase version that is installed running pip install oemoflex
[x] Test the examples
[x] Keep an eye on open issues that are set to your release but seem to be forgotten.
[x] Check that the docs look good.
Day of release
[x] Optional: Open a release branch to avoid conflicts with other uses while the release progress.
[x] Close "forgotten" issues with a recapitulatory comment or set them to a later release if they are still important.
[x] Test if everything works
If you have failing test fix them or postpone the release.
[x] Check the whatsnew-file
[x] Check if the latest documentation looks right at readthedocs.
[x] Change the version number everywhere!!! (e.g. from 0.2.1dev to 0.2.1) -> pyproject.yaml and docs/conf.py
[x] If everything seems to work, merge the release branch into the main branch. (--no-ff)
[x] Push your local main branch to the remote.
[x] Set a release on github. Select the main branch (default: dev)! A label is set automatically.
[x] Use git fetch to see the label in your local main branch.
[x] Merge the release branch into the dev branch. (--no-ff)
[x] Remove the obsolete release branch.
[x] Prepare the dev branch for further development: Adapt the version number at (e.g. from 0.2.1 to 0.2.2dev). Also add a new whatsnew file and a link in the whatsnew.rst file. Open the file locally or use the RAW button to see the links.
[x] Close the release issue with informations for the community and relax
Preparation
pip install oemoflex
Day of release
pyproject.yaml
anddocs/conf.py
git fetch
to see the label in your local main branch.