-
Notifications
You must be signed in to change notification settings - Fork 45
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
Release management / pyhector #202
Comments
Hi @rgieseke. We have a developmental branch <dev_doeclim> that I am currently working on merging into master. It incorporates a 1-D ocean diffusion model to better represent the oceanic heat uptake. This would be a major release for Hector. Like you mentioned we could time the release of pyhector with a new release of Hector. |
I thought it would be good if a patch like this were "released" faster, so "1.1.5". Are you planning on doing a 1.2 and a 2.0 release? Pyhector is currently based on the 1.2 branch ... |
@rgieseke I wanted to fill you in on our plan over the next 2 months. We will have a v1.2 that will incorporate a few issues and an old PR from you guys (We apologize for letting that one hang on for so long). After that we will have a v2.0 release which will have a significant update to the ocean heat uptake structure (currently a PR, working on some code cleanup). |
Many thanks for the update and apologies if I've been nagging too much! If there is anything I or @swillner can do to improve the PR or help testing let us know. |
We've made a patch release for Pyhector (as 0.8.1) with the halo-fix We'll have another release, once 1.2 or 2.0 are out! Closing this now, discussion on releases and branches can probably continue in #210 |
Hi,
I had a look at what difference the changes from #201 make (similar to earlier plots in issue #186):
This makes it seem worth updating Pyhector soon.
I could apply the patch like I did here for testing, but I'm wondering if you plan to apply this to the RC1.2 branch as well? Or if you have any plans to make releases more frequent. Ideally, we could target the current release with Pyhector.
Code I used below:
pyhector installed from git clone
pip install -e . pymagicc from pip pip install pymagicc
pyhector installed from git clone and patched with #201
The text was updated successfully, but these errors were encountered: