Joe Hamman

@jni - thanks for the feedback. I agree this is not ready to ship yet. The main things that we know are changing is the `Store` API and access to...

Here's my thought on `fsspec`. While I agree that the package dependency is not particularly large, it also don't come with batteries included -- you still need `s3fs`, `gcfs`, `adlfs`,...

There are some active threads on the subject already: - https://github.com/zarr-developers/numcodecs/issues/413 - https://github.com/zarr-developers/zarr-python/issues/713 Okay if we close this in favor of those open issues?

Cross posting https://github.com/zarr-developers/zarr-python/discussions/1480 where we are coordinating a group effort toward this ticket.

I've created a number of actionable tickets that can (hopefully) be addressed individually in an effort to bring Zarr-Python in sync with the spec. The current list includes: - [x]...

All the major tickets are closed here. See progress toward the v3 release here: https://github.com/orgs/zarr-developers/projects/5

@akshaysubr and @madsbk - we'd love to get this in. There's now a good list of (hopefully small) conflicts to resolve. Can we get this cleaned up this week?

@akshaysubr - I'm keen to get this in today or tomorrow if possible. Seems like we should just ignore the pre-commit errors once the ci issue noted above is addressed.

The fact that the `codecov` check is not passing is holding up a lot of important work. Can we fix this or disable the requirement? @joshmoore - if you want...

@aldenks - I wanted to also call out that @rabernat and others recently created this readme for v3 development: https://github.com/zarr-developers/zarr-python/blob/v3/README-v3.md