-
-
Notifications
You must be signed in to change notification settings - Fork 3
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
Comments
Should we warn on Twitter or other places ? After/Before ? |
I think announcing on Twitter after the release is sufficient.
…On Mon, Oct 14, 2019 at 2:19 PM Benjamin Zaitlen ***@***.***> wrote:
Should we warn on Twitter or other places ? After/Before ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#18?email_source=notifications&email_token=AAKAOIRSYA22NN7DJULTH73QOTA3LA5CNFSM4JAS6FSKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBGEG7Q#issuecomment-541868926>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAKAOIUQP5HYNDYBPD4T2MDQOTA3LANCNFSM4JAS6FSA>
.
|
Historically I haven't even been doing announcements on twitter (though I
think that it's a decent practice to get into)
On Mon, Oct 14, 2019 at 2:21 PM Tom Augspurger <notifications@github.com>
wrote:
… I think announcing on Twitter after the release is sufficient.
On Mon, Oct 14, 2019 at 2:19 PM Benjamin Zaitlen ***@***.***
>
wrote:
> Should we warn on Twitter or other places ? After/Before ?
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <
#18?email_source=notifications&email_token=AAKAOIRSYA22NN7DJULTH73QOTA3LA5CNFSM4JAS6FSKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBGEG7Q#issuecomment-541868926
>,
> or unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/AAKAOIUQP5HYNDYBPD4T2MDQOTA3LANCNFSM4JAS6FSA
>
> .
>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#18?email_source=notifications&email_token=AACKZTGWM4J6KFFJDEIX353QOTBEDA5CNFSM4JAS6FSKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBGEQLY#issuecomment-541870127>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACKZTAANJSTQQA2USARXJTQOTBEDANCNFSM4JAS6FSA>
.
|
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. |
@jrbourbeau did you want to handle this dask release or should I? |
I can push a dask 2.5.3 release later this afternoon. @mrocklin is it alright to have an accompanying distributed release? |
Yes. I think so. A release would be welcome.
…On Tue, Oct 15, 2019 at 12:02 PM James Bourbeau ***@***.***> wrote:
I can push a dask 2.5.3 release later this afternoon. @mrocklin
<https://github.com/mrocklin> is it alright to have an accompanying
distributed release?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#18?email_source=notifications&email_token=AACKZTCAOEZIH74TLQ3R5FLQOXZSPA5CNFSM4JAS6FSKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBJQEJI#issuecomment-542310949>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACKZTGCERELSIE27O3TATDQOXZSPANCNFSM4JAS6FSA>
.
|
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. |
assuming that we're comfortable releasing dask-kubernetes (@jacobtomlinson ) |
Yes I'll get a 0.10 realease out tomorrow unless someone else wants to do it before then. |
Sounds good, I'll wait until dask/distributed#3138 is in and then do a 2.6 release |
Dask and distributed 2.6.0 are on PyPI and conda-forge now. Thanks all! |
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
The text was updated successfully, but these errors were encountered: