-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WIP: Core protocol v3.0 development branch #16
Conversation
I added PR #17 with some work towards defining a conceptual model. |
Sorry, I might be missing something here. Does PR ( #17 ) replace this? |
…tual-model Core protocol v3.0 - conceptual model
No, sorry, #17 was working adding to this. I.e., #17 was a PR on this PR. I was thinking that we use this PR and branch ( |
I've added #24 with a straw man for a section on memory layouts. |
I've added #25 with a straw man for a section on node names. |
Co-authored-by: Norman Rzepka <code@normanrz.com>
Refactor codec specs into a single doc
Add minimal drafts of a few more dtype extensions
See open comments on #135 |
…-v3.0-dev As discussed during recent community meetings and steering council, merging this proposal into the dev branch as a common basis for discussions. The final list of features to be included in v3.0 is to be decided.
…tensions Structure spec pages and clarify extension points
I wonder if it would make more sense to merge this at this point as opposed to merging more PRs into this one. Understand there may still be rough edges and things we need to sort out still, but am just thinking about this practically. Please feel free to push back on this suggestion though @joshmoore @rabernat @alimanfoo, thoughts? 🙂 |
No objections. |
This is just about renaming the That seems fine since the master branch is currently unused. However, to avoid confusion it might be helpful to clarify in the "About" that this is about zarr v3 only, not zarr v2. |
👍 (Could even add a section on v2 with links, etc. to help people along) Waiting a day or two more for final thoughts then this can go in. readthedocs config will need updating at that same time. |
a7aa206
to
4153370
Compare
As mentioned. Merging and I'll tidy up the RTD configuration. All future branches should be against the mainline. |
This PR is intended as a focus for work on version 3.0 of the Zarr core protocol.
To contribute to this PR, please make a PR to the
core-protocol-v3.0-dev
branch. Please do not push changes directly to thecore-protocol-v3.0-dev
branch.Rendering docs from this branch can be viewed on RTFD.