Joe Hamman

Something we've seen a lot of in Zarr-Python 2 is unexpected traffic between the Group/Array APIs and the store. This ticket tracks the development of an instrumented store that will...

Some basic logging will really help with debugging Zarr. Specific objectives here: - [ ] develop common utility for generating a logger - [ ] add basic logging to array...

Zarr v3 will have a number of formal extension points and new options. This documentation ticket should explain how developers may choose to extend Zarr: Some sample topics: * how...

The v3 release doc should include: - a high level summary of the changes included - breaking changes - contributors Should we include the long list of PRs that went...

We need to write some documentation that clearly states how Zarr-Python v3 approaches consistency and synchronization. Topics to cover: - Concurrent readers and writers - Synchronization (async, threads, processes, distributed)...

We are not expecting many changes to the user experience as a part of v3 but a few things do come to mind as worth updating in the tutorial: -...

The introduction of two new top-level async classes (`AsyncGroup` and `AsyncArray`) plus significant changes to the `Store` API should be represented in the Zarr-Python docs by the time we make...

The v3 dev branch includes a number of new things that impact the developer experience. This ticket tracks the updating of the developer docs ahead of the 3.0 release.

Zarr will really benefit from some highly-parameterized stateful testing. @dcherian has been doing quite a bit of this work lately and could likely offer some ideas for impactful hypothesis strategies...

This can be a tricky thing to set up and get dependable results but it would be great to have something to help diagnose performance regressions. Ideas for how to...