My vote is +1 I ran dev/release/verify_release_candidate.sh 0.4.0 0 on MacOS M4 with the suggested workaround for GDAL 3.13.
Cheers, -dewey On Tue, Jun 23, 2026 at 12:42 PM Pranav Toggi <[email protected]> wrote: > > +1 (non-binding) > > [X] Downloaded the source tarball from dist [3] > [X] Verified the SHA512 checksum > [X] Verified the GPG signature against the project KEYS file > [X] Checked LICENSE, NOTICE, and DISCLAIMER > [X] Built from source and ran the unit tests on Linux (x86_64) via > `dev/release/verify-release-candidate.sh 0.4.0 0` > > > > On Jun 22, 2026, at 7:01 PM, Jia Yu <[email protected]> wrote: > > > > +1 binding > > > > [X] Downloaded the source tarball from dist [3] > > [X] Verified the SHA512 checksum > > [X] Verified the GPG signature against the project KEYS file > > [X] Checked LICENSE and NOTICE (DISCLAIMER N/A — Sedona is a TLP, not a > > podling) > > [X] Built from source and ran the unit tests on macOS arm64 (GDAL 3.13.1, > > --features bindgen) > > > > > > > > On Mon, Jun 22, 2026 at 16:44 James Willis <[email protected]> wrote: > > > >> +1 (non-binding) > >> > >> I verified the release candidate: > >> > >> [X] Downloaded the source tarball from dist [3] > >> [X] Verified the SHA512 checksum > >> [X] Verified the GPG signature against the project KEYS file > >> [X] Checked LICENSE, NOTICE, and DISCLAIMER > >> [X] Built from source and ran the unit tests on Linux (x86_64) via > >> `dev/release/verify-release-candidate.sh 0.4.0 0` > >> > >> I ran against GDAL 3.13 with the bindgen flag on macOS. I also ran through > >> the Zarr tutorial and the code from the release post for Zarr/ND arrays. > >> > >> > >> On Mon, Jun 22, 2026 at 10:04 AM Feng Zhang <[email protected]> wrote: > >> > >>> +1 (binding) > >>> > >>> I verified the release candidate: > >>> > >>> [X] Downloaded the source tarball from dist [3] > >>> [X] Verified the SHA512 checksum > >>> [X] Verified the GPG signature against the project KEYS file > >>> [X] Checked LICENSE, NOTICE, and DISCLAIMER > >>> [X] Built from source and ran the unit tests on Linux (x86_64) via > >>> `dev/release/verify-release-candidate.sh 0.4.0 0` > >>> > >>> On 2026/06/22 04:02:46 Dewey Dunnington wrote: > >>>> Hello, > >>>> > >>>> I would like to propose the following release candidate (rc0) of > >>>> Apache SedonaDB [0] version 0.4.0. This is a release consisting of 191 > >>>> resolved GitHub issues from 15 contributors [1]. > >>>> > >>>> This release candidate is based on commit: > >>>> b6f66a887eb77ab638b49eddd1aaaa6aebf353cd [2] > >>>> > >>>> The source release rc0 is hosted at [3]. > >>>> > >>>> Please download, verify checksums and signatures, run the unit tests, > >>>> and vote on the release. See [4] for how to validate a release > >>>> candidate. See [5] for a draft release post with release highlights. > >>>> > >>>> Note that users with a system install of GDAL 3.13 must export > >>>> SEDONADB_CARGO_TEST_ARGS="--features bindgen" as documented at [4]. > >>>> > >>>> The vote will be open for at least 72 hours. > >>>> > >>>> [ ] +1 Release this as Apache SedonaDB 0.3.0 > >>>> [ ] +0 > >>>> [ ] -1 Do not release this as Apache SedonaDB 0.3.0 because... > >>>> > >>>> [0] https://github.com/apache/sedona-db > >>>> [1] https://github.com/apache/sedona-db/milestone/3?closed=1 > >>>> [2] > >> https://github.com/apache/sedona-db/tree/apache-sedona-db-0.4.0-rc0 > >>>> [3] > >>> https://dist.apache.org/repos/dist/dev/sedona/apache-sedona-db-0.4.0-rc0 > >>>> [4] > >> https://github.com/apache/sedona-db/blob/main/dev/release/README.md > >>>> [5] https://github.com/apache/sedona/pull/3064 > >>>> > >>> > >> >
