Release on conda-forge

[aplowman]

[cjfullerton]

It looks like there's lots of in-house RSE experience of conda-forge releases - I'll ask for some pointers when we get round to this.

[cjfullerton]

Talk to Doug about this.

[fherreazcue]

Created recipe and got warning about valida not being available in conda-forge.

PR for valida created and waiting for conda staged-recipe's approval.

[fherreazcue]

Valida is now on condaforge and recipe is to be updated in the valida-feedstock.

[fherreazcue]

The PR for hpcflow is ready and waiting for approval.

[cjfullerton]

Return to this when we have a non-alpha release.

[fherreazcue]

As a guide for when this is done in the future:

The docs for contributions are pretty thorough.
In sum, you have to:

1. Create a branch on our fork of the staged-recipes repo.
2. Copy the recipes/example/ directory to a new directory with the package name, e.g. recipes/matflow/.
3. Generate the recipe (I used grayskull, as they suggest, but it can be done without it), and replace the text in recipes/matflow/meta.yaml with the generated recipe.
4. Add a recipes/matflow/LICENCE.txt file.
5. Test that it builds locally with python build-locally.py (the script is in the staged-recipes base directory)
6. Create a PR to the original staged-recipes repo, and complete the checklist.
7. Get the maintainers to comment on the PR agreeing to be maintainers.
8. Let conda know the PR is ready for review with a comment on the PR that mentions them, e.g. @conda-forge-admin, please ping @conda-forge/staged-recipes.

For valida this has already been done.
For hpcflow too, or at least mostly... the recipe needs updating with the non alpha or beta release, and ideally after the PyPI name change. Push the changes to the already existing branch, and the PR should be updated... ping the team again.
For matflow, we need hpcflow to be done first... I created the branch to save you some time, but it most definitely needs revision and updating, and there is no PR for it yet.

After the PR is merged, you get a feedstock repo (e.g. valida), which is where things are updated... but did not get to do that, so read the docs...