Making a release

This page is a memo for the Capytaine developer(s) detailing the process of doing a new release.

Last commit of released version

Open a pull request similar to https://github.com/capytaine/capytaine/pull/613 to update: - the version number in capytaine/__about__.py, - the changelog in docs/changelog.rst, - the link to previous documentations in docs/index.rst.

Dry-run packaging

Run it on version to be released.

to build the version of the master branch. The conda-forge CI will run the compilation. DO NOT merge the PR yet.

Github release and actual packaging

If the CI is all green, the PR can be merged and the package will be uploaded to the conda-forge repository in the following hours.

You’ll need the access token to PyPI.

Update documentation

In the repository of the website https://github.com/capytaine/capytaine.github.io, use the latest version of the documentation available in the directory master to make the new documentation and update the symlink stable:

mv master v2.1
rm stable
ln -s v2.1 stable
cp v2.0/_static/front_page_animation.webm v2.1/_static/

In the new version documentation (v2.1 in this example), remove the banner on top of the pages