Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release v0.20? #5889

Closed
TomNicholas opened this issue Oct 23, 2021 · 13 comments
Closed

Release v0.20? #5889

TomNicholas opened this issue Oct 23, 2021 · 13 comments
Labels
Release Planning and tracking progress of releases

Comments

@TomNicholas
Copy link
Member

TomNicholas commented Oct 23, 2021

We should do another release soon. The last one was v0.19 on July 23rd, so it's been 3 months.

(In particular I personally want to get some small pint compatibility fixes released such as #5571 and #5886, so that the code in this blog post advertising pint-xarray integration all works.)

There's been plenty of changes since then, and there are more we could merge quite quickly. It's a breaking release because we changed some dependencies, so should be called v0.20.0.

@benbovy how does the ongoing index refactor stuff affect this release? Do we need to wait so it can all be announced? Can we release with merged index refactor stuff just silently sitting there?

Small additions we could merge, feel free to suggest more @pydata/xarray :

@TomNicholas TomNicholas added the Release Planning and tracking progress of releases label Oct 23, 2021
@max-sixty
Copy link
Collaborator

I have been out of the loop for ages — thanks for others pulling up my slack — but I could help with this

@spencerkclark
Copy link
Member

It would be cool if we could merge #5233 before the next release as well. I think it is ready, and @aulemahal has been diligently working on it for the last several months (and been very patient with my sporadic reviewing frequency).

@benbovy
Copy link
Member

benbovy commented Oct 25, 2021

We should definitely make a release before #5692 gets merged. I've made good progress, but it's not ready yet. It'll also be safer to have one last stable release before merging all those changes. Once it is merged, we'll probably need a few release candidates and beta testers to ensure that we don't break important use cases that CI didn't caught.

@mathause
Copy link
Collaborator

Could also be good to fix #5721 before the release. @benbovy are you still up for this?

@TomNicholas
Copy link
Member Author

TomNicholas commented Oct 28, 2021

@keewis there is a note in whats-new.rst:

.. TODO(by keewis): update deprecations if we decide to skip 0.19.1

We are going to be skipping 0.19.1 because we have breaking changes, so I'm just flagging that so it doesn't get forgotten.

@dcherian
Copy link
Contributor

It'd be nice to get #5911 in since that adds a new dependency and this is a major version

@dcherian
Copy link
Contributor

It looks like we can bump minimum versions on a bunch of packages if someone is up for doing it:

Package           Required             Policy               Status
----------------- -------------------- -------------------- ------
cartopy           0.17    (2018-11-17) 0.18    (2020-07-09) <
cftime            1.1     (2020-03-15) 1.2     (2020-07-05) <
dask              2.24    (2020-08-24) 2.30    (2020-10-07) <
distributed       2.24    (2020-08-22) 2.30    (2020-10-07) <
hdf5              1.10    (2017-09-18) 1.12    (2020-08-03) <
lxml              4.5     (2020-01-29) 4.6     (2020-10-17) <
matplotlib-base   3.2     (2020-03-04) 3.3     (2020-07-20) <
numba             0.49    (2020-04-17) 0.51    (2020-08-17) <
numpy             1.17    (2019-08-01) 1.18    (2020-01-16) <
pandas            1.0     (2020-01-29) 1.1     (2020-07-28) <
pint              0.15    (2020-08-22) 0.16    (2020-09-14) <
scipy             1.4     (2019-12-19) 1.5     (2020-06-23) <
seaborn           0.10    (2020-01-31) 0.11    (2020-09-08) <
sparse            0.8     (2019-08-26) 0.11    (2020-08-18) <
toolz             0.10    (2019-07-12) 0.11    (2020-09-24) <
zarr              2.4     (2020-01-11) 2.5     (2020-10-08) <

@TomNicholas
Copy link
Member Author

It looks like we can bump minimum versions on a bunch of packages if someone is up for doing it:

What does this involve?

@keewis
Copy link
Collaborator

keewis commented Oct 29, 2021

What does this involve?

Updating the two min deps conda environment files and listing the changes in whats-new.rst is usually enough, but for numpy and pandas we need to update setup.cfg. There might be also some compatibility code that can be removed, and documentation pages that need to be updated, though.

@keewis
Copy link
Collaborator

keewis commented Nov 1, 2021

do we know where the failures in #5919 are coming from? It would probably be good to fix them before the release...

@TomNicholas
Copy link
Member Author

Update the docs. Login to https://readthedocs.org/projects/xray/versions/ and switch your new release tag (at the bottom) from "Inactive" to "Active". It should now build automatically.

I did all the other steps, but I don't see the v0.20.0 release tag on readthedocs 😕

I cancelled a workflow that I thought was superfluous - was it actually needed?

@dcherian
Copy link
Contributor

dcherian commented Nov 2, 2021

I see it. Activating...

@TomNicholas
Copy link
Member Author

TomNicholas commented Nov 2, 2021

Oh I see it now too.

Are we done then? Is v0.20.0 supposed to appear in the dropdown menu in the lower-right of the main docs page?

EDIT: I see it now. Consider this release done!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Release Planning and tracking progress of releases
Projects
None yet
Development

No branches or pull requests

7 participants