You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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
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 dask/distributed#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 dask/distributed#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.
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.
Activity
jrbourbeau commentedon May 31, 2022
@fjetter should I put dask/distributed#6480 down as a blocker?
jakirkham commentedon Jun 1, 2022
Not Florian, but given this is done maybe it is worth noting it is at least complete
jacobtomlinson commentedon Jun 6, 2022
Now that we've done the rebrand of Dask the
latestdocs are using the new theme and logo. Thestabledocs 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.jrbourbeau commentedon Jun 6, 2022
We can also just manually trigger a new
stabledocs 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 themejacobtomlinson commentedon Jun 6, 2022
Ooh good point. That would be great. Do you mind handling that @jrbourbeau ?
jrbourbeau commentedon Jun 6, 2022
https://docs.dask.org/en/stable/ and https://distributed.dask.org/en/stable/ have both been rebuilt and are using the new theme now 👍
jrbourbeau commentedon Jun 7, 2022
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 dask/distributed#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 inmain. @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 dask/distributed#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
crusaderky commentedon Jun 8, 2022
Blocker: dask/distributed#6528
jacobtomlinson commentedon Jun 8, 2022
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.
jrbourbeau commentedon Jun 9, 2022
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
jakirkham commentedon Jun 10, 2022
Think we may want to get PR ( dask/distributed#6557 ) in
TomAugspurger commentedon Jun 10, 2022
Just flagging dask/distributed#6559 / dask/dask-gateway#573, which is breaking dask-gateway at the moment.
jrbourbeau commentedon Jun 10, 2022
@TomAugspurger pushed up a fix for dask/distributed#6559 over in dask/distributed#6561
mrocklin commentedon Jun 10, 2022
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.
jakirkham commentedon Jun 10, 2022
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
jakirkham commentedon Jun 10, 2022
Sounds like PR ( dask/distributed#6557 ) is not a blocker. So if there are no other blockers, should be good to go ahead
jrbourbeau commentedon Jun 10, 2022
Will start pushing out the release in the next hour and will ping here when the release is on PyPI
jrbourbeau commentedon Jun 10, 2022
Alright, 2022.6.0 is out on PyPI and conda-forge PRs have been opened
jrbourbeau commentedon Jun 11, 2022
Docker images and conda-forge packages for this release are now out. Thanks all!