-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Comments
I have been out of the loop for ages — thanks for others pulling up my slack — but I could help with this |
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). |
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. |
@keewis there is a note in
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. |
It'd be nice to get #5911 in since that adds a new dependency and this is a major version |
It looks like we can bump minimum versions on a bunch of packages if someone is up for doing it:
|
What does this involve? |
Updating the two min deps conda environment files and listing the changes in |
do we know where the failures in #5919 are coming from? It would probably be good to fix them before the release... |
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? |
I see it. Activating... |
Oh I see it now too. Are we done then? Is EDIT: I see it now. Consider this release done! |
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 :
The text was updated successfully, but these errors were encountered: