Releasing xtl

Releasing a new version

From the relevant branch of xtl

  • Make sure that you are in sync with the master branch of the upstream remote.

  • In file xtl_config.hpp, set the macros for XTL_VERSION_MAJOR, XTL_VERSION_MINOR and XTL_VERSION_PATCH to the desired values.

  • In file README.md, modify the binder link to point to the new release.

  • Stage the changes (git add), commit the changes (git commit) and add a tag of the form Major.minor.patch. It is important to not add any other content to the tag name.

  • Push the new commit and tag to the main repository. (git push, and git push --tags)

Updating the conda-forge recipe

xtl has been packaged for the conda package manager. Once the new tag has been pushed on GitHub, edit the conda-forge recipe for xtl in the following fashion:

  • Update the version number to the new Major.minor.patch.

  • Set the build number to 0.

  • Update the hash of the source tarball.

  • Check for the versions of the dependencies.

  • Optionally, rerender the conda-forge feedstock.