0.0.19 release?

[raybellwaves]

I think we are overdue a release.

Any PR's we should merge/issues we should close before release?

@aaronspring has two open PR's that would be good get in

• add deterministic xr-metrics to asv benchmark and asv refactor #231

• ROC #236

also @ahuang11

• Test raise if compute #224

Lastly

• adapt RPS #277

[aaronspring]

maybe we wait for the next xr release and then only drop py36?

[raybellwaves]

Sounds good. I've always wondered if there was a bot that could post on an issue to tell you when a package was updated. cc. @jacobtomlinson if he has any thoughts.

[jacobtomlinson]

You could definitely set something up with GitHub Actions. We do this in some Dask repos to open PRs to bump pinned versions on release.

But for a one off like this you may just want to use IFTTT.

• If "RSS feed gets new item" (xarray tags RSS feed)
• Then "Open issue on repo"

[aaronspring]

after #221 we are ready

[aaronspring]

After #277 i would like to see a new release. #266 is an embarrassing bug. Which other PRs should we waiting for?

[raybellwaves]

Once #277 goes in I think we should release. #221 doesn't have to be a bottleneck for this release (i've removed it from my original comment).

[aaronspring]

I would be grateful for a new release @raybellwaves

[raybellwaves]

You are welcome to release. I believe you have credentials. @bradyrx did the last release and can guide. He has some nice notes heres: https://xskillscore.readthedocs.io/en/latest/release_procedure.html. The only thing that may be different this time is conda-forge/xskillscore-feedstock#20