dask / community

For general discussion and community planning. Discussion issues welcome.
19 stars 3 forks source link

Release 2023.2.1 #308

Closed jrbourbeau closed 1 year ago

jrbourbeau commented 1 year ago
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 commented 1 year ago

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 https://github.com/conda-forge/dask-core-feedstock/issues/160 and https://github.com/conda-forge/dask-feedstock/issues/214 are the only things out of the ordinary for conda-forge this release

fjetter commented 1 year ago

Currently waiting for CI to finish for

and will start with the release afterwards

fjetter commented 1 year ago

Done.

cc @charlesbluca

charlesbluca commented 1 year ago

Opened PRs across the feedstocks:

Also noting that some pinnings on distributed and dask weren't updated to reflect the changes made in https://github.com/dask/distributed/pull/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 commented 1 year ago

There is one regression that may warrant a patch release, see https://github.com/dask/dask/pull/10005

jrbourbeau commented 1 year ago

Thanks @fjetter @charlesbluca for pushing this release out!

There is one regression that may warrant a patch release, see https://github.com/dask/dask/pull/10005

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