Prepare for Dask 2.3.0 release

[jrbourbeau]

This is just to test against the current master branch of dask/dask and dask/distributed prior to releasing 2.3.0 upstream

[mrocklin]

Thanks for handling this @jrbourbeau . I hope that this work all gets replaced in the near-to-moderate future with the SpecCluster rewrite (#307) , but until then it's quite nice to maintain continuity.

[jrbourbeau]

Thanks for pointing me to #307, looking forward to seeing it included

until then it's quite nice to maintain continuity

Just to be clear, you mean continuity with distributed right? Fortunately, it looks like adding a scheduler_info attribute was the only addition needed for compatibility with the current distributed master

[mrocklin]

Yes, I mean that it'll be nice to make sure that things continue to work for users while we continue to work on the SpecCluster rewrite. I hope that *after* that rewrite, the dask-jobqueue package becomes much smaller and requires less maintenance.

…

On Wed, Aug 14, 2019 at 7:50 PM James Bourbeau ***@***.***> wrote: Thanks for pointing me to #307 <#307>, looking forward to seeing it included until then it's quite nice to maintain continuity Just to be clear, you mean continuity with distributed right? Fortunately, it looks like adding a scheduler_info attribute was the only addition needed for compatibility with the current distributed master — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#313?email_source=notifications&email_token=AACKZTAE2PRR2EDH4JH5MHDQESK5TA5CNFSM4ILYO6IKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4KNZII#issuecomment-521460897>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AACKZTGRSFJDBXDPNIW75JDQESK5TANCNFSM4ILYO6IA> .

[jrbourbeau]

the dask-jobqueue package becomes much smaller
and requires less maintenance

+1 😄

Things look good here (the CI is passing against upstream masters), so I'll go ahead and revert back to testing against the latest release

[mrocklin]

Thanks @jrbourbeau !

[mrocklin]

@guillaumeeb is it ok if I push out a release for dask 2.3 compatibility?

[guillaumeeb]

Sure! No problem from me. We have to ensure that jobqueue is compatible with the latest Dask version!

[mrocklin]

Done

…

On Sun, Aug 18, 2019 at 12:39 PM Guillaume Eynard-Bontemps < ***@***.***> wrote: Sure! No problem from me. We have to ensure that jobqueue is compatible with the latest Dask version! — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#313?email_source=notifications&email_token=AACKZTCBT3Z4DQ75DXSSLCTQFF3MFA5CNFSM4ILYO6IKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4RDTLQ#issuecomment-522336686>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AACKZTE7WA3VKSKLCFH2F6DQFF3MFANCNFSM4ILYO6IA> .

[lesteve]

Thanks for this! FYI I pushed a minor change in the changelog to make it more clear that dask-jobqueue 0.6.3 is compatible with dask 2.3.0