Release ?

[guillaumeeb]

#63 has been merged after the previous release. I think we should make a new one to account this change and other smaller ones. Moreover, without #63, adaptive seems to be broken as highlighted in #126, and probably #122.

[guillaumeeb]

ping @mrocklin @jhamman @lesteve

Maybe we should wait for #118 #131 and #135, that should get in soon.

[lesteve]

What is the status of #97? I haven't followed closely but my feeling is that adaptative still have some quirks that would be nice to iron out.

[jhamman]

Status of #97. Not done. Could use some beta testers / new ideas. We can make a release without those changes but I'd like to make sure a few others understand the complications therein.

[guillaumeeb]

I think we should move on and release soon. I've never done that, but can try tomorrow.

[mrocklin]

I would be happy to help walk you through it. I typically follow the checklist here: https://github.com/dask/dask/blob/master/docs/release-procedure.md

I'll need to add you as a maintainer of the project on PyPI. Do you have an account there already?

[guillaumeeb]

Nope, don't think so, will create it.

[guillaumeeb]

Done, same login as github.

[mrocklin]

You should now have push access to PyPI. Do the steps in the release procedure doc make sense to you?

…

On Wed, Sep 5, 2018 at 3:41 PM, Guillaume EB ***@***.***> wrote: Done, same login as github. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#127 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AASszD6eiut9kvz1Fp31ev_-H5HMlEoxks5uYCjOgaJpZM4V9Fw7> .

[guillaumeeb]

Generally yes. Don't know twine though, and conda forge part looks a bit more complex, but that should be ok.

[mrocklin]

You should be able to just pip install twine and then follow instructions.

…

On Wed, Sep 5, 2018 at 4:00 PM, Guillaume EB ***@***.***> wrote: Generally yes. Don't know twine though, and conda forge part looks a bit more complex, but that should be ok. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#127 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AASszFyn9UB02YSAKQljdCjVYl0XAWj3ks5uYC1IgaJpZM4V9Fw7> .

[guillaumeeb]

Perfect, will try tomorrow and get to you if I encounter some issue. Thanks !

That leaves some hours for others to chime in if against a release now.

[willirath]

conda forge part looks a bit more complex

This is not necessarily true any more: You can skip the rerendering part and trigger this with a comment in the discussion after creating the PR with just the recipe/meta.yaml updated to the new version (hash, version number, reset build number):

https://conda-forge.org/docs/webservice.html#conda-forge-admin-please-rerender

[mrocklin]

Conda forge bots will also probably pick up the change once it's on PyPI. I recommend pushing to PyPI and then waiting for a while to see what happens.

…

On Thu, Sep 6, 2018 at 3:38 AM, Willi Rath ***@***.***> wrote: conda forge part looks a bit more complex This is not necessarily true any more: You can skip the rerendering part and trigger this with a comment in the discussion after creating the PR with just the recipe/meta.yaml updated to the new version (hash, version number, reset build number): https://conda-forge.org/docs/webservice.html#conda-forge- admin-please-rerender — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#127 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AASszLOl88lMlYIYrwaqiNPcrGrwRuWSks5uYNDigaJpZM4V9Fw7> .

[guillaumeeb]

dask-jobqueue (0.4.0) pushed to PyPI.

Waiting for conda-forge as recommended by @mrocklin.

[guillaumeeb]

Done!