Less restrictive pins in release version

[ntabris]

The current release of dask-cuda is pinned to dask/distributed 2022.03.0.

There's a merged PR to unpin these "for development" (#892) which implies that they're going to be pinned again for release.

Is there a reason for the exact pinning? The PR that pinned these (#878) says it's to be in line with cuDF and the PR that pinned for cuDF gave no reason.

[pentschev]

Yes, Dask provides no API guarantees. Dask-CUDA is the backbone of RAPIDS and just allowing Dask-CUDA release package to pick the latest Dask/Distributed is guaranteed to be a source of problem after a few (or even just one) release. Therefore we need to pin to a version that we test and is known to work.

Before every RAPIDS release we decide what Dask/Distributed release is stable and pin that version, which we then unpin when we begin working on the new branch for the upcoming RAPIDS release.

[pentschev]

We have a discussion about this in #848 as well.

[github-actions]

This issue has been labeled inactive-30d due to no recent activity in the past 30 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed. This issue will be labeled inactive-90d if there is no activity in the next 60 days.

[github-actions]

This issue has been labeled inactive-90d due to no recent activity in the past 90 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed.

[pentschev]

Given this isn't something we are likely to change due to the reasons in #911 (comment) and since there has been no further discussions, I'm closing this issue. Please feel free to reopen if needed.