Skip to content

Latest commit

 

History

History
42 lines (22 loc) · 1.3 KB

HOW_TO_RELEASE.md

File metadata and controls

42 lines (22 loc) · 1.3 KB
  1. Create a new branch and PR to prepare for release:

    git checkout -b releaseX.Y

    1. Run codespell from repo root and fix errors:

      codespell -q 2

    2. Make sure that all CI tests are passed with *free environments

    3. Update ./requirements.txt and ./docs/requirements.txt with CI free environments dependencies versions

    4. Update ./ci/requirements/py*-dev.yml with last free environments dependencies versions

    5. Make sure that all CI tests are passed with *dev environments

    6. Increase release version in ./setup.py file

    7. Update date and release version in ./docs/whats-new.rst

    8. Merge PR to master:

      git checkout master

      git merge releaseX.Y

  2. On the master branch, commit the release in git:

    git commit -a -m 'Release v0.X.Y'

  3. Tag the release:

    git tag -a v0.X.Y -m 'v0.X.Y'

  4. Push it online:

    git push origin v0.X.Y

  5. Issue the release on GitHub. Click on "Draft a new release" at https://github.com/euroargodev/argopy/releases. Type in the version number v0.X.Y, and click on the auto-generate a release note button.

    This will trigger the publish Github action that will push the release on Pypi.