Closed jrbourbeau closed 2 years ago
@fjetter should I put https://github.com/dask/distributed/issues/6480 down as a blocker?
should I put dask/distributed#6480 down as a blocker?
Not Florian, but given this is done maybe it is worth noting it is at least complete
Now that we've done the rebrand of Dask the latest
docs are using the new theme and logo. The stable
docs will continue to use the old theme and logo until the next release, so it would be great to get this out as soon as we can.
We can also just manually trigger a new stable
docs build if we want to get the new theme out ASAP. That should build the docs from the same commit as the previous release, but should pull in the new theme
Ooh good point. That would be great. Do you mind handling that @jrbourbeau ?
https://docs.dask.org/en/stable/ and https://distributed.dask.org/en/stable/ have both been rebuilt and are using the new theme now 👍
Just wanted to check in here to see if folks have any known blockers we should be aware of before releasing this Friday.
In an offline conversation earlier today, @crusaderky mentioned that the worker state machine refactor (xref https://github.com/dask/distributed/issues/6476) is getting close and some substantial PRs related to this effort are about to land in distributed
. Because of this, I proposed we hold off on merging those PRs until after releasing on Friday to give those changes time to simmer in main
. @crusaderky was okay with this and didn't think it would slow down development meaningfully.
@crusaderky I've added the remaining PRs that link to https://github.com/dask/distributed/issues/6476 to a new "Merge after releasing" section at the top of this issue. Let me know if that looks good, or if there are any adjustments I should make
This probably isn't a huge issue but all NVIDIA staff are OOTO thu/fri this week. So if there are last-minute release issues fewer folks will be around.
Just following up here. All reported blockers have been resolved so, unless a new blocker pop up, I'll push out the 2022.6.0 release tomorrow
Think we may want to get PR ( https://github.com/dask/distributed/pull/6557 ) in
Just flagging https://github.com/dask/distributed/issues/6559 / https://github.com/dask/dask-gateway/pull/573, which is breaking dask-gateway at the moment.
@TomAugspurger pushed up a fix for https://github.com/dask/distributed/issues/6559 over in https://github.com/dask/distributed/pull/6561
Think we may want to get PR ( https://github.com/dask/distributed/pull/6557 ) in
My read is that this isn't something that was inserted in the last release. I'm not sure that it should block. However, if @jakirkham or someone has time to engage and review then that would of course be grand.
Right if our understanding is correct, it has been there a while. Just took the quick issue and PR as an indication of something pressing.
Have already been reviewing
Sounds like PR ( https://github.com/dask/distributed/pull/6557 ) is not a blocker. So if there are no other blockers, should be good to go ahead
Will start pushing out the release in the next hour and will ping here when the release is on PyPI
Alright, 2022.6.0 is out on PyPI and conda-forge PRs have been opened
Docker images and conda-forge packages for this release are now out. Thanks all!
Given the 2022.05.2 patch release last Thursday, I'll propose we push our normal two week release cadence back one week and have our next release on June 10. Opening up a tracking issue early than usual to give ample notice
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
Merge after releasing
Comments
cc @jsignell @jakirkham @fjetter @quasiben