Conda

General Process

1. Developer clones code from GIT
2. Developer makes changes in feature branch and makes pull request
3. Once the CI is passing on the feature branch and the pull request, the code is re based and merged in.
4. When there are enough new features to warrant a new version, a tag for the new version is created (i.e. 1.3.5)
   • The tag will automatically trigger of the conan package builds, we have to manually change the conda builds.
5. In the conda-recipes repository find the recipe for the library you are updating.
6. In the meta.yml file for the recipe change the version number and the sha256 hash to match the new version.
   • The sha number can be found by downloading the tar.gz from github and using sha256sum on linux to get the hash
7. Commit the changes to the conda recipe and the CI will build and publish the new conda package.