-
-
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 2022.03.0 #231
Comments
It would be great to get dask/dask#8648 in |
There's a regression in Dask-CUDA which I'd like to fix before releasing: |
I don't want to put undo pressure on the reviewers, so if dask/distributed#5904 isn't ready yet, we can postpone the release. |
Two more regressions (actual impact yet to be triaged): |
Ok thanks for reporting @crusaderky . I am going to say let's delay the relase until next week. |
How are things looking generally? With respect to PR ( dask/distributed#5904 ), think we are waiting for a final review. Would be good to get that in :) |
|
Based on the conversation here I am planning on releasing today, just waiting on those 3 linked issues. |
The dask tests just started failing on GPU CI. So I want to get confirmation that that is not a real issue before kicking off this release. |
gpuCI issue is now addressed. xref: dask/dask#8826 |
I am going to delay this release. We can talk next week about whether doing it on Friday, March 25 is good enough, or if we want to do it earlier in the week. |
closed both |
Should we go ahead given those are resolved or do you think we should still wait? |
I am planning on starting the release unless there is a reason not to? |
SGTM |
Ok starting release! |
uploaded to pypi |
Thanks @jakirkham for merging those up! |
Dask docker PR is merged, so I'm closing this up. Thanks everyone! |
If there aren't any known blockers, I'd like to release
dask
anddistributed
2022.03.0
on Friday.cc @jakirkham @quasiben @jsignell @fjetter @crusaderky @jrbourbeau
The text was updated successfully, but these errors were encountered: