Release 2023.2.1

[jrbourbeau]

Release version	2023.2.1
Planned release date	2023-02-24
Status	On-track
Release manager	@fjetter

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

As a heads up I'll be on PTO this Friday, so I've asked Florian to take care of this release (thank you Florian!)

cc @fjetter @rjzamora @quasiben @jakirkham

[jrbourbeau]

Just a heads up, I spoke to @charlesbluca offline and he's happy to handle the conda-forge and dask-docker parts of the release on Friday. So Florian, no need to worry about those.

@charlesbluca conda-forge/dask-core-feedstock#160 and conda-forge/dask-feedstock#214 are the only things out of the ordinary for conda-forge this release

[fjetter]

Currently waiting for CI to finish for

• Enable P2P shuffling by default dask#9991
• P2P rechunking dask#9939
• P2P for array rechunking distributed#7534

and will start with the release afterwards

[fjetter]

Done.

cc @charlesbluca

[charlesbluca]

Opened PRs across the feedstocks:

• Release 2023.2.1 conda-forge/dask-core-feedstock#161
• Release 2023.2.1 conda-forge/distributed-feedstock#242
• Release 2023.2.1 conda-forge/dask-feedstock#215

Also noting that some pinnings on distributed and dask weren't updated to reflect the changes made in dask/distributed#7285, so I've gone ahead and changed them in these PRs. Once these are merged in, I can go ahead and submit a repodata patch to update the constraints of the affected packages (essentially all distributed/dask packages from 2022.1.0 to 2022.2.0)

[fjetter]

There is one regression that may warrant a patch release, see dask/dask#10005

[jrbourbeau]

Thanks @fjetter @charlesbluca for pushing this release out!

There is one regression that may warrant a patch release, see dask/dask#10005

Thanks for the heads up -- will open up a separate issue for this