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/6645#issuecomment-1151261404,https://api.github.com/repos/pydata/xarray/issues/6645,1151261404,IC_kwDOAMm_X85Entrc,14808389,2022-06-09T15:20:39Z,2022-06-09T15:20:39Z,MEMBER,"I just published the pre-release, it can be installed from PyPI:
```python
mamba create -n python=3.10 xarray
python -m pip install --pre --upgrade --no-deps xarray
```
(the `--no-deps` is important, otherwise we pull the pre-releases of other packages)","{""total_count"": 3, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 3, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,1250755592
https://github.com/pydata/xarray/issues/6645#issuecomment-1144982336,https://api.github.com/repos/pydata/xarray/issues/6645,1144982336,IC_kwDOAMm_X85EPwtA,14808389,2022-06-02T15:13:21Z,2022-06-02T15:20:34Z,MEMBER,"As far as I remember the only reason we don't do that already is that `setuptools_scm` creates nightly version strings that are not compliant to PEP440. The version scheme appears to be configurable, but I couldn't find documentation on how to do that. As such, if anyone can figure out how to create PEP440 (and thus PyPI) compatible development versions I think we can have a CI publish every commit on `main` to TestPyPI.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,1250755592
https://github.com/pydata/xarray/issues/6645#issuecomment-1143377823,https://api.github.com/repos/pydata/xarray/issues/6645,1143377823,IC_kwDOAMm_X85EJo-f,14808389,2022-06-01T09:47:41Z,2022-06-01T09:47:41Z,MEMBER,"right, I misunderstood that MVCE. I still think that we don't need to wait on a fix to do the pre-release, though.
As far as I understand PEP440, to create a pre-release we just need add a `rcN` suffix (i.e. `2022.06.0rc0`) or `.devN` (i.e. `2022.06.0.dev0`. Do we need to update `whats-new.rst` for this?","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,1250755592
https://github.com/pydata/xarray/issues/6645#issuecomment-1140243610,https://api.github.com/repos/pydata/xarray/issues/6645,1140243610,IC_kwDOAMm_X85D9rya,14808389,2022-05-28T11:36:43Z,2022-05-28T11:37:14Z,MEMBER,"the `cftime` issues (#6624, #6613) look like they would be good to be fixed first, but since the remaining one (#6607) is also in `2022.3.0` I don't think we need to wait on that for the pre-release.
Something to remember, though, is that this is *not* a full release, so I don't think we need to have fixed every known bug / regression.","{""total_count"": 1, ""+1"": 1, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,1250755592