Release 2022.4.2

[jrbourbeau]

If there are no blockers I'd like to release dask and distributed 2022.4.2 this Friday as part of our usual release cadence. In particular, it would be good to get some pandas compatibility updates (for the next pandas release) out (xref dask/dask#8961) as well as a fix for a reported deadlock (xref dask/distributed#6110).

I know @jcrist @rjzamora @ian-r-rose @bryanwweber are working on changing the default values for some parquet-related keyword arguments. @jcrist mentioned offline it would be good to include all those changes in the same release. @jcrist what's in flight that you'd like to see included?

@mrocklin @fjetter @crusaderky there's been a lot of activity in distributed since the last release. How are things looking for releasing this Friday? Are there specific PRs you explicitly want to see included or not included in this release?

cc @jsignell @quasiben @jakirkham

[rjzamora]

On the parquet side it would be ideal to merge dask/dask#8988 and dask/dask#8992 as close together as possible (as well as the related doc changes).

It would also be good to get dask/dask#8989 in since it's currently blocking dask-sql CI (another from_delayed surprise).

Status:

• dask#8988 (merged)
• dask#8992 (merged)
• dask#8989 (merged)

[crusaderky]

• Worker stuck in closing_gracefully state distributed#6223 should be treated as a blocker. ETA for a fix is this Friday.

[rjzamora]

Given this comment from @ian-r-rose in the from_delayed fix, I wonder if anyone is interested in trying to include the from_map PR (dask/dask#8911) in this release (with a clear warning that the API is experimental in the docstring)? This way we could encourage users to "kick the tires" and provide feedback sooner rather than later?

No pressure from me at all - Just interested in other perspectives.

[EDIT: On second thought, I don't think there is any great reason to rush on from_map. So, feel free to ignore the comment above :) ]

[fjetter]

I am trying to find reviewers for the two PRs. If we can get them in before the release, that would be big

• Race conditions from fetch to compute while AMM requests replica distributed#6248
• Ensure resumed tasks are not accidentally forgotten distributed#6217

Edit: We just had a conversation about the two PRs and we prefer not to rush them in right now but rather take our time for proper review.

[jrbourbeau]

Alright, it looks like all the parquet-related PRs are in and I see dask/distributed#6223 is closed (good work everybody 🎉). @fjetter I'm interpreting #240 (comment) as those PRs shouldn't block the release, is that correct?

[mrocklin]

Correct. I think that you're good to go @jrbourbeau

[mrocklin]

It's a good point to note that we're clearing out a few non-trivial failures these days on distributed. We might want to ask for an accelerated release in the future.

[jrbourbeau]

Sounds good -- going to start pushing the release out now...

[jrbourbeau]

2022.4.2 is out. Thanks all!

[mrocklin]

Woo!

…

On Fri, Apr 29, 2022 at 10:18 PM James Bourbeau ***@***.***> wrote: 2022.4.2 is out. Thanks all! — Reply to this email directly, view it on GitHub <#240 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACKZTGEPUUQ3KPR2BY6HWTVHSQ7JANCNFSM5UQ3MFBQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>