-
-
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
release 0.17.0 #4894
Comments
Thanks @dcherian! I agree those would be good to get in too. |
@alexamici no target date AFAIK. it'd be nice to release soon since there are incompatibilities with a few new library versions |
Unless we're really confident that a feature is a few days away, I'd vote to generally proceed with releases. Releases are fairly cheap to do now (and I'm happy to do them), and uncoupling parts of the process lets it move faster. Ofc if we have regressions, then we should solve those. (I have been under a crunch recently but can hopefully help more in a week or so) |
May I suggest #4740 as well. I think it's ready and it helps me quite a bit in my 2k+ data variable use cases. |
@max-sixty will cut a release this weekend. @alexamici can you get the PR in by then? If not, we can release again! and again! |
This would be really great. But if it doesn't fit now, I hope a release will be cut right after finalising backend refactor. This is an eagerly awaited addition. |
I don't think we will be ready by this week-end and we don't want to rush the switch to the new API without some thorough testing by others. We will wait for the next release. |
No worries, @alexamici, as the API can be switched to v2 already, this is no major problem. Better safe than sorry wrt testing. Thank you and your colleagues! |
#4849 should be almost ready to go. Would be good for someone else to confirm the API makes sense. Additional features and performance enhancements could be added in later releases as long as the API is acceptable. |
There is a small mis-formatting in "whats-new", that would be good to fix: http://xarray.pydata.org/en/latest/whats-new.html |
if you're talking about the versions table: this should be fixed in #4907 |
Yes that's the one - thanks! |
Thanks @max-sixty ! |
Quoting @spencerkclark email:
These three seem like high-priority fixes. Thoughts?
Nice to have
The text was updated successfully, but these errors were encountered: