Skip to content

Conversation

@jpn--
Copy link
Member

@jpn-- jpn-- commented Jun 21, 2021

This branch contains work on #424

@jpn-- jpn-- marked this pull request as draft June 21, 2021 18:26
jpn-- added 3 commits June 21, 2021 15:10
because I can't seem to write one command correctly, why, why why
@coveralls
Copy link

coveralls commented Jun 22, 2021

Coverage Status

Coverage decreased (-0.07%) to 56.275% when pulling 74b1fcc on jpn--:condaforge-dev into a57efa1 on ActivitySim:master.

@bstabler
Copy link
Contributor

includes work on #437 as well

@jpn-- jpn-- marked this pull request as ready for review June 30, 2021 12:46
@jpn--
Copy link
Member Author

jpn-- commented Jun 30, 2021

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.

@jpn-- jpn-- changed the title Condaforge dev Improved distribution system for conda-forge and pip Jul 9, 2021
@bstabler
Copy link
Contributor

bstabler commented Jul 9, 2021

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.

@jpn--
Copy link
Member Author

jpn-- commented Jul 13, 2021

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants