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/3926#issuecomment-608015240,https://api.github.com/repos/pydata/xarray/issues/3926,608015240,MDEyOklzc3VlQ29tbWVudDYwODAxNTI0MA==,14808389,2020-04-02T18:02:12Z,2020-04-02T18:02:12Z,MEMBER,"thanks, @TomNicholas, looks good to me.

I opened #3928 for the `upstream-dev` failures.","{""total_count"": 1, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 1, ""rocket"": 0, ""eyes"": 0}",,592331420
https://github.com/pydata/xarray/pull/3926#issuecomment-608010931,https://api.github.com/repos/pydata/xarray/issues/3926,608010931,MDEyOklzc3VlQ29tbWVudDYwODAxMDkzMQ==,14808389,2020-04-02T17:54:09Z,2020-04-02T17:57:28Z,MEMBER,"> The warning messages said ""will no longer accept"" and ""will require"" in ""version 0.15"" - that's probably authoritative enough isn't it?

I'd think so, yes. Rereading what the warnings are intended for, [`FutureWarning`](https://docs.python.org/3/library/exceptions.html#FutureWarning) is indeed the same as [`DeprecationWarning`](https://docs.python.org/3/library/exceptions.html#DeprecationWarning), the only difference is the intended target audience. I seem to have confused `FutureWarning` with `PendingDeprecationWarning`.

Then my only issue is with the `whats-new.rst` entry. I'd explicitly state that `auto_combine` was removed.

Edit: sorry, you also mentioned that. The way I understood ""deprecating"" was what you meant with ""starting the deprecation cycle"", so that's where the confusion came from.","{""total_count"": 1, ""+1"": 1, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,592331420