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

make pypi and conda packages for 0.3.0 #47

Closed
1 task done
gidden opened this issue Mar 17, 2022 · 8 comments
Closed
1 task done

make pypi and conda packages for 0.3.0 #47

gidden opened this issue Mar 17, 2022 · 8 comments
Assignees

Comments

@gidden
Copy link
Member

gidden commented Mar 17, 2022

  • pypi
  • [ ] conda
@gidden
Copy link
Member Author

gidden commented Mar 17, 2022

cc @khaeru - could we put this on a future support request please?

@khaeru
Copy link
Member

khaeru commented Mar 17, 2022

cc @khaeru - could we put this on a future support request please?

Sorry, I'm not sure what's meant by this. Do you want to assign me?

@gidden
Copy link
Member Author

gidden commented Mar 17, 2022

No, I don't want to assign you but rather put this on the docket for IIASA ECE dev ops support. Perhaps I should be cc'ing @danielhuppmann as well?

@khaeru
Copy link
Member

khaeru commented Mar 17, 2022

Okay, understood. That can be broken down into two kinds of work:

  1. Bringing the packaging, tooling, CI config, Slack integration, etc., for this repo in line with what we use across our other repos.
  2. Ongoing maintenance.

For ixmp, message_ix, message-ix-models, and message_data, @LauWien and I have invested heavily in (1) to make them as uniform as possible. This eases (2) significantly, because the maintenance/updates/fixes can be applied by copy-paste (or nearly so); the same well-described release procedure works for all the repos, etc.

Depending on how active development is here, (2) is probably manageable in the long term (at least, it is not bigger than our other resource allocation problems). But (1) could be a sizeable chunk of work in the short term; it depends on the current state of the package, with which I'm not familiar. IMO it would be easiest if you (or someone you can find) approached (1) by copying from the other repos, and then asked us to review the result and continue with (2) once merged.

@gidden
Copy link
Member Author

gidden commented Mar 17, 2022

Thanks @khaeru - pinged the wrong group. Feel free to delegate as useful @danielhuppmann, thanks!

@jkikstra
Copy link
Collaborator

Great, thanks for this.
Just commenting to keep up-to-date, such that I can merge in a PR on the climate-assessment repo when this is done

@gidden
Copy link
Member Author

gidden commented May 13, 2022

@jkikstra - latest aneris now on pip thanks to @danielhuppmann ! I couldn't find a conda-forge feedstock, so don't think it was ever there (which is fine).

@gidden gidden closed this as completed May 13, 2022
@jkikstra
Copy link
Collaborator

Thank you @danielhuppmann and @gidden for notifying me, great!

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

No branches or pull requests

4 participants