John Ericson f0adb72c23 Mark fetchTree as unstable again ... As discussed in our last meeting, we need a bit more time, but we are "time boxing" the work left to do to ensure there is not unbounded delay. Rather than putting it back underneath `flakes`, though, put it underneath its own `fetch-tree` experimental feature (which `flakes` includes/implies). This signals our commitment to the plan to stabilize it first without waiting to go through the rest of Flakes, and also will give users a "release candidate" when we get closer to stabilization. This reverts commit 4112dd1fc9.		2023-11-08 23:23:56 -05:00
..
internal-api	Factor out bits of the worker protocol to use elsewhere	2023-10-09 16:55:12 -04:00
manual	Mark fetchTree as unstable again	2023-11-08 23:23:56 -05:00