-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Things to complete before releasing xarray v0.9.0 #1167
Comments
Are we pushing #964? This would be awesome to start building on, although important to get right given it'll be a platform |
I also really want to merge #964 (the "apply" function) but the current API is a little too confusing. We could merge it without exposing it as public API for now and/or start building simplified versions (e.g., with an optional I agree that it should be a top priority but I don't want to let it hold up 0.9 any longer, so I think we should release without it. |
I have two smaller features I'd like to get in:
These are both pretty close and could be wrapped up in a day or so. |
There is never an ideal time to make a release cut, but this has been dragging on for too long. I just sent out an email announcing a release candidate for v0.9.0: Unlimited dimensions will have to wait to the v0.9.1 release, but that release can follow pretty shortly given that the changes should be mostly backwards compatible. |
@shoyer Do you plan to push a release tarball for |
@ghisvail Oops, I forgot to upload the source distribution to pypi (now fixed). The final release should be some time this week, up to you if you want to wait. |
If I wrap up this thread, I see we are missing:
|
With the merge of #1222, I plan to issue the new release tonight or tomorrow morning (pending a successful doc build and a final check-over). |
It is picky but it might be worth to pin mpl to v2 for nicer plots in the docs ;-) Am I allowed to try it out? |
Certainly, give it a try!
…On Tue, Jan 24, 2017 at 1:28 PM, Fabien Maussion ***@***.***> wrote:
It is picky but it might be worth to pin mpl to v2 for nicer plots in the
docs ;-) Am I allowed to try it out?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1167 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABKS1qt-_CC_qfNcXHNEOa5tIfTETEHEks5rVm0WgaJpZM4LOzyA>
.
|
Not that this matters greatly to xarray, but I am happy to report that the latest master causes no problems with xmitgcm, which, because of the custom DataStore, is a somewhat obscure edge case. Full speed ahead with the release! |
@rabernat the DataStore refactor will happen sometime soon I hope, but I will definitely coordinate with you! |
@shoyer - glad this is coming together. Let me know if you'd like any help with the release steps. |
@shoyer I've tested mpl on the |
The built docs look pretty good to me, so I think we can go ahead with
matplotlib 2.0: http://xarray.pydata.org/en/fix-docs/plotting.html
…On Tue, Jan 24, 2017 at 2:29 PM, Fabien Maussion ***@***.***> wrote:
@shoyer <https://github.com/shoyer> I've tested mpl on the fix-docs
branch and they seem to build properly (see the dashboard
<https://readthedocs.org/projects/xray/builds/>), but for some reason
xarray's webpage is unreachable right now so I can't see how it looks like.
It's getting late here in central europe so if you want to make the release
later today go ahead, MPL2 can wait.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1167 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABKS1osL4YAfEmseT8ogKRvIqmlcSFywks5rVntWgaJpZM4LOzyA>
.
|
I think we can close this because 0.9.0 has been released. |
set_index
,reset_index
andreorder_levels
methods Addset_index
,reset_index
andreorder_levels
methods #1028@pydata/xarray anything else essential?
The text was updated successfully, but these errors were encountered: