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/pull/2591#issuecomment-445787568,https://api.github.com/repos/pydata/xarray/issues/2591,445787568,MDEyOklzc3VlQ29tbWVudDQ0NTc4NzU2OA==,6628425,2018-12-10T11:43:36Z,2018-12-10T11:43:36Z,MEMBER,">  How about whats-new.rst, do you want me to fill in something there?

Yes, I think it would make sense to document this change under the ""Bug fixes"" heading.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,387732534
https://github.com/pydata/xarray/pull/2591#issuecomment-445781253,https://api.github.com/repos/pydata/xarray/issues/2591,445781253,MDEyOklzc3VlQ29tbWVudDQ0NTc4MTI1Mw==,6628425,2018-12-10T11:18:11Z,2018-12-10T11:18:11Z,MEMBER,"> Ok travis seems to pass, how about appveyor ? There are many time encoding errors, should it be so ?

I believe those are unrelated to this PR.  There was a [series of bug fix releases of cftime](https://github.com/Unidata/cftime/releases) following the initial 1.0.3 release (the failing build here uses 1.0.3).   I think with the latest one (1.0.3.4), released a few days ago, things should be back to normal (as evidenced by the build passing in #2596).","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,387732534