id,node_id,number,title,user,state,locked,assignee,milestone,comments,created_at,updated_at,closed_at,author_association,active_lock_reason,draft,pull_request,body,reactions,performed_via_github_app,state_reason,repo,type
1519552711,PR_kwDOAMm_X85GqAro,7418,Import datatree in xarray?,35968931,closed,0,,,18,2023-01-04T20:48:09Z,2023-12-22T17:38:04Z,2023-12-22T17:38:04Z,MEMBER,,0,pydata/xarray/pulls/7418,"I want [datatree](https://github.com/xarray-contrib/datatree) to live in xarray main, as right now it's in a separate package but imports many xarray internals.

This presents a few questions:
1) At what stage is datatree ""ready"" to moved in here? At what stage should it become encouraged public API?
2) What's a good way to slowly roll the feature out?
3) How do I decrease the bus factor on datatree's code? Can I get some code reviews during the merging process? :pray: 
4) Should I make a new CI environment just for testing datatree stuff?

Today @jhamman and @keewis suggested for now I make it so that you can `from xarray import DataTree`, using the current xarray-datatree package as an optional dependency. That way I can create a smoother on-ramp, get some more users testing it, but without committing all the code into this repo yet.

@pydata/xarray what do you think? Any other thoughts about best practices when moving a good few thousand lines of code into xarray?

- [x] First step towards moving solution of  #4118 into this repository
- [x] Tests added
- [x] User visible changes (including notable bug fixes) are documented in `whats-new.rst`
- [x] New functions/methods are listed in `api.rst`
","{""url"": ""https://api.github.com/repos/pydata/xarray/issues/7418/reactions"", ""total_count"": 6, ""+1"": 4, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 2}",,,13221727,pull