id,node_id,number,title,user,state,locked,assignee,milestone,comments,created_at,updated_at,closed_at,author_association,active_lock_reason,draft,pull_request,body,reactions,performed_via_github_app,state_reason,repo,type
200125945,MDU6SXNzdWUyMDAxMjU5NDU=,1199,Document the new __repr__,10050469,closed,0,,2244472,23,2017-01-11T15:37:37Z,2017-01-30T17:41:34Z,2017-01-30T17:41:34Z,MEMBER,,,,"Sorry I missed that one when it was decided upon in https://github.com/pydata/xarray/pull/1017, but I think the changes in ``repr`` should be documented somewhere (at the minimum in the ""Breaking Changes"" section of what's new).

I just updated Salem for it to work well with xarray 0.9.0. The changes I had to make where quite small (that's a good thing), but it took me a bit of time to understand what was going on. 

What I found confusing is following:

```python
In [1]: import xarray as xr
In [2]: ds = xr.DataArray([1, 2, 3]).to_dataset(name='var')
In [3]: ds
Out[3]: 
<xarray.Dataset>
Dimensions:  (dim_0: 3)
Coordinates:
  o dim_0    (dim_0) -
Data variables:
    var      (dim_0) int64 1 2 3

In [4]: 'dim_0' in ds.coords
Out[4]: False
```
``dim_0``is listed as coordinate, but ``'dim_0' in ds.coords`` is ``False``. I think it should remain like this, but maybe we should document somewhere what the ""o"" and ""*"" mean? 

(possibly [here](http://xarray.pydata.org/en/latest/data-structures.html#creating-a-dataset))
","{""url"": ""https://api.github.com/repos/pydata/xarray/issues/1199/reactions"", ""total_count"": 1, ""+1"": 1, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,completed,13221727,issue
203018953,MDExOlB1bGxSZXF1ZXN0MTAzMDU5OTA0,1228,Doc and build fixes for v0.9.0,1217238,closed,0,,2244472,0,2017-01-25T05:54:26Z,2017-01-26T04:12:49Z,2017-01-26T04:12:49Z,MEMBER,,0,pydata/xarray/pulls/1228,"Fixes #858
Fixes #925

xref #1167","{""url"": ""https://api.github.com/repos/pydata/xarray/issues/1228/reactions"", ""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,,13221727,pull
201762650,MDU6SXNzdWUyMDE3NjI2NTA=,1218,Testing functions should be moved to a separate `xarray.testing` module,1217238,closed,0,,2244472,4,2017-01-19T04:33:14Z,2017-01-24T21:18:20Z,2017-01-24T21:18:20Z,MEMBER,,,,"These functions are in the `test` module, which isn't imported by default because it requires `pytest`, which we only require for testing. Hence the API docs are currently broken:
http://xarray.pydata.org/en/latest/api.html#testing

If we move these to a separate `testing` module (i.e., a `testing.py` file), we can make `xarray.testing.assert_xarray_equal` just work after `import xarray` (maybe rename it to just `xarray.testing.assert_equal` to avoid the redundant `xarray`).

To avoid confusion, we might rename the `test` directory to `tests`.

cc @MaximilianR @fmaussion in case either of you want to take a look at this -- it should probably be a blocker for 0.9.0.","{""url"": ""https://api.github.com/repos/pydata/xarray/issues/1218/reactions"", ""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,completed,13221727,issue