Closed jrbourbeau closed 1 year ago
It looks like issue ( https://github.com/dask/distributed/issues/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 https://github.com/dask/distributed/issues/7173
@jrbourbeau yes, I think distributed is good to release
$ git log 2022.11.0..main --oneline
69b74f9f Remove exception handling from transitions (#7316)
26c92407 Fix typo in `client.run()` docstring (#7315)
44423d0a Always raise exception if P2PShuffle's send fails (#7317)
5cba6625 Turn private functions into private `SchedulerState` methods (#7260)
5635bc01 Note queuing default change in changelog (#7314)
176a84cb Bump `toolz` minimum version to `0.10.0` (#7309)
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
2022.11.1
is on PyPI. Will open up conda-forge PRs
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
Comments
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 https://github.com/dask/dask/pull/9673 and https://github.com/dask/distributed/pull/7329 which reinstate thebokeh<3
version restriction. See https://github.com/dask/distributed/issues/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