use DataTree from xarray instead of from xarray-datatree #24
Conversation
OriolAbril
force-pushed
the
xarray_datatree
branch
from
edfd962
to
a27f0a4
Compare
There was a problem hiding this comment.
LGTM
I would not merge this to main though, since it has breaking changes. Let's make a "0.3.0" branch and merge to that. Then we can sync with the other packages using the 0.3.0 branch to fix problems. For each project, we should make a "0.3.0" branch as well, and any fixes that go into them using this branch, should be merged into their respective 0.3.0 branches. Once all bugs have been ironed out, we can push each 0.3.0 branch into main, tag, and then release.
|
I was thinking about making a 0.3 release before merging, then using 0.4.0.dev0 as version on main and merging this. But at this stage I would not worry too much about releases nor breaking changes. For arviz-devs/arviz-stats#16 for example my idea was also to directly do the change in arviz-stats, update arviz-plots as needed and consider it done, no warnings or duplication of dim/dims |
related to #14. I wouldn't merge just yet, and instead merge as many PRs as possible,
create similar PRs in arviz-stats and arviz-plots to pull the band aid.
📚 Documentation preview 📚: https://arviz-base--24.org.readthedocs.build/en/24/