Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update release process to use conda-forge #396

Closed
forsyth2 opened this issue Jan 27, 2023 · 1 comment · Fixed by #410
Closed

Update release process to use conda-forge #396

forsyth2 opened this issue Jan 27, 2023 · 1 comment · Fixed by #410
Labels
DevOps CI/CD, configuration, etc. Documentation Files in `docs` modified

Comments

@forsyth2
Copy link
Collaborator

Update GitHub Actions and https://e3sm-project.github.io/zppy/_build/html/main/dev_guide/release.html#releasing-anaconda to reflect the new conda-forge process (see conda-forge/staged-recipes#21883).

From @xylar: we would need to remove the GitHub actions that make the build for the e3sm anaconda channel. Then, you would change the sections about anaconda to instead refer to waiting for a bot PR to come up automatically on conda-forge after the GitHub release. A maintainer would then update the dependencies on conda-forge to match the conda/meta.yaml file for the GitHub release and merge the conda-forge PR.

@forsyth2 forsyth2 added semver: small improvement Small improvement (will increment patch version) DevOps CI/CD, configuration, etc. Documentation Files in `docs` modified and removed semver: small improvement Small improvement (will increment patch version) labels Jan 27, 2023
@xylar
Copy link
Contributor

xylar commented Feb 8, 2023

It is time to make these changes (before the next release), now that there is a zppy feedstock:
https://github.com/conda-forge/zppy-feedstock/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DevOps CI/CD, configuration, etc. Documentation Files in `docs` modified
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants