Conversation
Headings and front matter in the 3.3.0 house style, with the proposed highlights, evidence, PR references and snippet ideas as markdown comments for the prose to be written against. Marked draft: true so it is excluded from the built site until it is ready. Assisted-by: ClaudeCode:claude-fable-5-1
… handles Prose for the stack, roadmap, rectilinear, codec-error and msgspec sections; typo and grammar fixes; PR/issue links throughout; a runnable example of the new unknown-codec error; contributors listed by GitHub handle with first-time contributors marked. The 3.3.0 post gains the same contributor section for its own release range. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
github-actions
Bot
added
the
needs release notes
ilan-gold
left a comment
ilan-gold
left a comment
There was a problem hiding this comment.
This looks great but I'd love to see it on the website rendered. Otherwise, I don't spot anything out of place
i'll take it out of draft, I think that gets you the preview |
ilan-gold
left a comment
ilan-gold
left a comment
There was a problem hiding this comment.
the lack of intersphinx in markdown (which IIRC is a result of not using sphinx?) kills me! There are so many useful links to have here!
| print(e) | ||
| ``` | ||
|
|
||
| The table lives in `zarr.registry`; if you maintain a package that provides a codec, please add it there. |
There was a problem hiding this comment.
Would be awesome to have inter sphinx here or a link, at least! Unrelated, on that page, it is not really clear what the registry is for.
There was a problem hiding this comment.
I added an internal link to the registry API docs
Co-authored-by: Ilan Gold <ilanbassgold@gmail.com>
2 participants
This is a blog post for the 3.4.0 release. I wrote it. Please have a look!
🤖 AI text below 🤖
Summary
Release blog post for
zarr3.4.0, in the format of the 3.3.0 post: the project becoming a stack of packages (zarr-metadata,zarr-indexing,zarr-http-server, with the chunk-key-encoding, storage and codec packages in flight), the new roadmap, the rectilinear chunk grid improvements, the codec errors that now name the package to install (with a runnable example of the message), and the newmsgspecdependency. Contributors are listed by GitHub handle with first-time contributors marked, and the 3.3.0 post gains the same contributor section for its own range, which it had omitted.The post is marked
draft: truein its front matter, so it is excluded from the built site until that line is removed at publication time; the strict docs build passes with it present, the executable example runs under the docs test harness, and the cross-link to the 3.3.0 post was verified to resolve in a build with the draft flag temporarily off.The post's title uses
zarr, not "Zarr-Python", deliberately: with the subpackages, Zarr-Python names the project, and the release is of thezarrpackage.For reviewers
Prose is the author's; the rest of the branch is copy edits, links, the codec-error example, and the contributor lists. Remove
draft: truewhen the release is tagged so the post publishes with it.Author attestation
TODO
docs/user-guide/*.md(n/a)changes/(n/a — blog post, as for 3.3.0)🤖 Generated with Claude Code