Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dask Release #18

Closed
TomAugspurger opened this issue Oct 14, 2019 · 12 comments
Closed

Dask Release #18

TomAugspurger opened this issue Oct 14, 2019 · 12 comments

Comments

@TomAugspurger
Copy link
Member

I'd like to propose a release for dask to fix a syntax compatibility issue with Python 3.5.

@quasiben has fixed the issue on Dask master.

Is there anything else worth waiting on, or should we do a release soon?

xref dask/dask#5447

@quasiben
Copy link
Member

Should we warn on Twitter or other places ? After/Before ?

@TomAugspurger
Copy link
Member Author

TomAugspurger commented Oct 14, 2019 via email

@mrocklin
Copy link
Member

mrocklin commented Oct 14, 2019 via email

@jacobtomlinson
Copy link
Member

Unless you specifically want to include information about the release in the tweet it is quite straight forward to set up something like IFTTT to automatically tweet when a new tag is created on GitHub. GitHub has an RSS feed of all tags for a project so you can use that as the triggering source.

@TomAugspurger
Copy link
Member Author

@jrbourbeau did you want to handle this dask release or should I?

@jrbourbeau
Copy link
Member

I can push a dask 2.5.3 release later this afternoon. @mrocklin is it alright to have an accompanying distributed release?

@mrocklin
Copy link
Member

mrocklin commented Oct 15, 2019 via email

@mrocklin
Copy link
Member

If you haven't started already I suggest that we merge in the dashboard refactor, and then call this 2.6. We might then write up a quick blogpost about the ssh/jobqueue/kubernetes rewrite as part of the release.

@mrocklin
Copy link
Member

assuming that we're comfortable releasing dask-kubernetes (@jacobtomlinson )

@jacobtomlinson
Copy link
Member

Yes I'll get a 0.10 realease out tomorrow unless someone else wants to do it before then.

@jrbourbeau
Copy link
Member

If you haven't started already I suggest that we merge in the dashboard refactor, and then call this 2.6

Sounds good, I'll wait until dask/distributed#3138 is in and then do a 2.6 release

@jrbourbeau
Copy link
Member

jrbourbeau commented Oct 16, 2019

Dask and distributed 2.6.0 are on PyPI and conda-forge now. Thanks all!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants