-
-
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? #7069
Comments
It would be nice to be able to go back to what we were doing recently, i.e. releasing every 2 weeks (after each dev meeting). Will we be able to go back to that schedule after this release? (I can release this next version too) |
Looks like this is a good time to release! @TomNicholas can you handle this one please? |
Should we wait to fix any of the other regressions? Or just fix them in the next release. Are we doing any kind of announcement about indexes with this release? Or just summarise whatsnew as normal? Also kind of unrelated (I forgot to mention this in the meeting today) but can someone please add my columbia email (thomas dot nicholas at columbia dot edu)to the xarray dev team google group/list? I think it was attached to my old institutional address which has since lapsed. |
I think we can go ahead with the release. The remaining regressions seem to affect only a limited number of use cases ; it could wait the following release if we we are not waiting too long between the two. I'd also wait for an announcement about indexes. It has been already announced at the previous release, and it'd probably be better to communicate about it (maybe via a blog post?) after improving the docs and experimenting a bit more with custom indexes... |
What is your issue?
It's been 3 months since our last release.
We still have quite a few regressions from the last release but @benbovy does have open PRs for a number of them. However, we do have some nice bugfixes and other commits in the mean time.
I propose we issue a new release, perhaps after @benbovy merges the PRs he thinks are ready.
I'll be out of town for the next few days, so if someone else could volunteer to be release manager that would be great!
The text was updated successfully, but these errors were encountered: