html_url,issue_url,id,node_id,user,created_at,updated_at,author_association,body,reactions,performed_via_github_app,issue
https://github.com/pydata/xarray/issues/2203#issuecomment-393401980,https://api.github.com/repos/pydata/xarray/issues/2203,393401980,MDEyOklzc3VlQ29tbWVudDM5MzQwMTk4MA==,1217238,2018-05-31T04:55:00Z,2018-05-31T04:55:00Z,MEMBER,"The policy I've tried to keep to is keeping everything working with base
supported version, but we can add new features that rely on new dask
features.
On Wed, May 30, 2018 at 8:20 PM Keisuke Fujii
wrote:
> How do we consider the minimum version of *optional* dependency?
> If we say ""the minimum version of dask is 0.16"", then all our dask related
> functions should work with dask=0.16?
> or do we allow functions that only work with newer version of dask if we
> raise an appropriate error message?
>
> —
> You are receiving this because you are on a team that was mentioned.
> Reply to this email directly, view it on GitHub
> , or mute
> the thread
>
> .
>
","{""total_count"": 1, ""+1"": 1, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,327893262
https://github.com/pydata/xarray/issues/2203#issuecomment-393357662,https://api.github.com/repos/pydata/xarray/issues/2203,393357662,MDEyOklzc3VlQ29tbWVudDM5MzM1NzY2Mg==,1217238,2018-05-31T00:02:01Z,2018-05-31T00:02:08Z,MEMBER,"Requiring 0.15.4 seems reasonable to me. There is virtue in supporting a (small) range of versions in dependencies. But clearly 0.9 was too out of date here.
We should probably add a CI test against the oldest version of dask that we support, just to make sure things don't sneak through.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,327893262