2.13.4 release notes

[joshmoore]

Kicking off the release process. Comments on which scope ("maintenance", "major", etc) each PR should belong to welcome. Thanks to @MSanKeys963 for drafting this over the holidays! 🎉

[joshmoore]

@MSanKeys963: thoughts on adding a blurb at the top of the release with a pointer to one or more of the outreachy blogs? Also, we'll need to think about the contributors list.

[sanketverma1704]

Thanks for sending the PR, @joshmoore.

thoughts on adding a blurb at the top of the release with a pointer to one or more of the outreachy blogs?

Are you mentioning this one: https://zarr.dev/blog/welcoming-outreachy-2022-interns/?
Or @caviere's and @DON-BRAN's blogs?

Also, we'll need to think about the contributors list.

AFAIK, there's some work done by @GbotemiB in #1185 for this. @GbotemiB, do you wish to complete this PR anytime soon?

[sanketverma1704]

Suggested a few minor edits above. ^

[joshmoore]

Are you mentioning this one: https://zarr.dev/blog/welcoming-outreachy-2022-interns/?

Yes, since there were lots of contributions from the wider outreachy community.

[sanketverma1704]

@jakirkham, do you think we can get #1285 in this release?

[joshmoore]

I'm going to review the rendered outreachy blurb, @MSanKeys963, and then go ahead and move forward with this as a patch release. ensure_bytes can follow up either as another quick patch release or as a minor release.

[rabernat]

Why not get #1285 in? This is really important to our contributors at scalable minds.

[joshmoore]

It's on @jakirkham's list to review, and the release notes were done for the things merged so it makes sense to get those out before things get tricky again. (Releases are easy; notes are [currently] hard)