-
-
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.11.1 #292
Comments
It looks like issue ( dask/distributed#7327 ) is closed. Should it be reopened if it is a live issue? |
That issue (and a couple others) have been closed as duplicates of dask/distributed#7173 |
@jrbourbeau yes, I think distributed is good to release
Also the bokeh PRs look green and ready to merge FYI. |
Great -- thanks again for you work here @gjoseph92. Given the current time, let's release tomorrow morning-ish US time |
Alright, the two linked PRs are in -- I'm going to push out the release in ~1 hour |
|
conda-forge packages and docker images are out -- thanks all! |
Best effort
Try to close before the release but will not block the release
Blocker
Issues that would cause us to block and postpone the release if not fixed
bokeh=3
support dask#9673bokeh=3
support distributed#7329Comments
Recently we relaxed our
bokeh
version constraints to allowbokeh=3
. I think this was a bit too premature (my fault) and I'd like to push out a quick patch release with dask/dask#9673 and dask/distributed#7329 which reinstate thebokeh<3
version restriction. See dask/distributed#7327 for more context.dask/dask
is in a good place for releasing. Looking atgit log
fordask/distributed
I don't see anything that's been merged since the last release that's particularly controversial and would block releasing (cc @fjetter @gjoseph92).cc @jakirkham @charlesbluca @quasiben for visibility
The text was updated successfully, but these errors were encountered: