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
Improved distribution system for conda-forge and pip #440
Conversation
because I can't seem to write one command correctly, why, why why
includes work on #437 as well |
Any objection to merging this PR into master, and tagging it as v1.0.2? This PR is operationally identical to 1.0.1, just with the dependencies fixed so orca is a dependency and zbox is gone. To make a clean version for conda-forge for #424, conda-forge policy (very reasonably) wants to build code as it appears from the main repo and not a PR. |
As discussed 7/8, we can't publish to conda forge until the code is in master, but having the code in master also means we've released the code according to our Release Process. So, @jpn-- is updating the docs as if these changes are live, and we're working on some additional improvements to make releases more automated - for example, #139. |
I can only work on #139 in a branch of the main repo, not on my fork. So, closing this in favor of the same branch I've pushed now the the main repo. |
This branch contains work on #424