-
-
Notifications
You must be signed in to change notification settings - Fork 3
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 2021.06.0 #162
Comments
SGTM It would be good if we can get some people to test some of these fixes (meta in particular). I don't think we were aware of this widespread usage. So it would be good to confirm we've gotten this right this time and aren't making it worse for people (even if that means moving a little slower potentially) More generally it seems there may be different expectations of how meta should be or can be used. It might be worth coming up with intended usage and improving documentation and APIs as was done with Dask Custom Collections. This may need to be a separate issue/discussion though |
Feedback from others would be great. I've reached out to most of the projects listed in dask/dask#7743 (comment) which were known to be impacted by the latest release. FWIW dask/dask#7743 should restore the same behavior (by default) for |
It would also be good to get the |
Alright, all PRs mentioned in this issue have been merged. I'm going to start pushing out the release |
Closing as |
Thanks James! 😀 |
A couple of issues have been reported with the 2021.06.0 release (xref dask/dask#7731, rapidsai/dask-cuda#634) which both have fixes in the works. If there are no other blockers, I'd like to release tomorrow or Friday after the PRs which fix these issues (listed below) have been merged:
cc @quasiben @jakirkham @jsignell
The text was updated successfully, but these errors were encountered: