Release 1.3.0 or 2.0.0?

[maxrjones]

Should we release VirtualiZarr now so that people can use it with Zarr-Python 3.0, or wait until after phase 2 (Migrate to zarr_format=3) of the ongoing Zarr-Python 3.0 migration project? If we wait, would the release need to be v2.0.0 rather than 1.3.0 due to the breaking changes since the last release (https://virtualizarr.readthedocs.io/en/latest/releases.html#v1-2-1-unreleased) and the major changes to ManifestArray associated iwth #411?

[TomNicholas]

Good question, but I think before we release anything we should fix compatibility with the latest version of Icechunk.

breaking changes since the last release

I think these constitute minor changes, so would be v1.3.0.

major changes to ManifestArray

Including these would definitely justify bumping the major version to v2.0.0.

[maxrjones]

Thanks, I forgot about the upstream issue. I think it's still good to have this open now so that non-devs have awareness of our release schedule.

[TomNicholas]

We now are about to have everything green! Also icechunk has now released 0.1.0, so we're out of the alpha series. I suggest we:

• Merge Fix tests by recreating the repo every time #417
• Update Icechunk dependency to 0.1.0 and fix anything that crops up
• Release virtualizarr 1.3.0
• Then work on the rest of the zarr-python v3 stuff in preparation for releasing virtualizarr 2.0.0.

[TomNicholas]

Actually icechunk just released 0.1.1

[TomNicholas]

I just released v1.3.0, so will close this.