The vote carries with 7 binding +1s!

I'll get started on the post-release tasks:

[ ] Closed GitHub milestone
[ ] Added release to the Apache Reporter System
[ ] Uploaded artifacts to Subversion
[ ] Created GitHub release
[ ] Submit R package to CRAN
[ ] Submit Python package to PyPI
[ ] Update Python package on conda-forge
[ ] Update the WrapDB entry
[ ] Update the vcpkg port
[ ] Update release documentation
[ ] Release blog post at https://github.com/apache/arrow-site/pull/661
[ ] Sent announcement to annou...@apache.org
[ ] Removed old artifacts from SVN
[ ] Bumped versions on main

On Thu, Jul 3, 2025 at 12:05 PM Dewey Dunnington <dewey.dunning...@gmail.com>
wrote:

> Thanks all for verifying!
>
> My vote is +1 (binding). I ran ./verify-release-candidate.sh 0.7.0 1 on
> MacOS 15.5. I also ran a suite of validation runs for this RC on our CI [1].
>
> [1] https://github.com/apache/arrow-nanoarrow/actions/runs/15963160549
>
> On Wed, Jul 2, 2025 at 7:22 AM Alenka Frim <frim.ale...@gmail.com> wrote:
>
>> +1
>>
>> Verified on macOs 15.5 M1 by running
>> `> dev/release/verify-release-candidate.sh 0.7.0 1`
>> `Release candidate 0.7.0-RC1 looks good!` =)
>>
>> V V tor., 1. jul. 2025 ob 09:22 je oseba Raúl Cumplido <rau...@apache.org
>> >
>> napisala:
>>
>> > +1 (binding)
>> >
>> > I ran:
>> >
>> >  $ dev/release/verify-release-candidate.sh 0.7.0 1
>> >
>> > on Ubuntu 24.04.
>> >
>> > Raúl
>> >
>> > El mar, 1 jul 2025 a las 5:59, Gang Wu (<ust...@gmail.com>) escribió:
>> >
>> > > +1
>> > >
>> > > Verified on my macOS
>> > >
>> > > BTW, I think [1] is
>> > > https://github.com/apache/arrow-nanoarrow/milestone/7?closed=1
>> > >
>> > > On Tue, Jul 1, 2025 at 9:21 AM Sutou Kouhei <k...@clear-code.com>
>> wrote:
>> > >
>> > > > +1 (binding)
>> > > >
>> > > > I ran the following on Debian GNU/Linux sid:
>> > > >
>> > > >   dev/release/verify-release-candidate.sh 0.7.0 1
>> > > >
>> > > > with:
>> > > >
>> > > >   * g++ (Debian 14.2.0-19) 14.2.0
>> > > >   * Python 3.13.5
>> > > >   * R version 4.5.1 (2025-06-13) -- "Great Square Root"
>> > > >
>> > > >
>> > > > Thanks,
>> > > > --
>> > > > kou
>> > > >
>> > > > In <
>> can040pa4exo-cwyv561awmog2ug2ww1si36z+hv_mmgngtj...@mail.gmail.com
>> > >
>> > > >   "[VOTE] Release nanoarrow 0.7.0 RC1" on Mon, 30 Jun 2025 10:49:21
>> > > -0500,
>> > > >   Dewey Dunnington <paleolim...@apache.org> wrote:
>> > > >
>> > > > > Hello,
>> > > > >
>> > > > > I would like to propose the following release candidate (rc1) of
>> > Apache
>> > > > > Arrow nanoarrow [0] version 0.7.0. This is an initial release
>> > > consisting
>> > > > of
>> > > > > 117 resolved GitHub issues from 12 contributors [1].
>> > > > >
>> > > > > This release candidate is based on commit:
>> > > > > 2cfba631b40886f1418a463f3b7c4552c8ae0dc7 [2]
>> > > > >
>> > > > > The source release rc1 is hosted at [3].
>> > > > > The changelog is located at [4].
>> > > > >
>> > > > > Please download, verify checksums and signatures, run the unit
>> tests,
>> > > and
>> > > > > vote on the release. See [5] for how to validate a release
>> candidate.
>> > > > Note
>> > > > > that Arrow C++ is no longer required for release verification.
>> > > > >
>> > > > > The vote will be open for at least 72 hours.
>> > > > >
>> > > > > [ ] +1 Release this as Apache Arrow nanoarrow 0.7.0
>> > > > > [ ] +0
>> > > > > [ ] -1 Do not release this as Apache Arrow nanoarrow 0.7.0
>> because...
>> > > > >
>> > > > > [0] https://github.com/apache/arrow-nanoarrow
>> > > > > [1]
>> https://github.com/apache/arrow-nanoarrow/milestone/4?closed=1
>> > > > > [2]
>> > > > >
>> > > >
>> > >
>> >
>> https://github.com/apache/arrow-nanoarrow/tree/apache-arrow-nanoarrow-0.7.0-rc1
>> > > > > [3]
>> > > > >
>> > > >
>> > >
>> >
>> https://dist.apache.org/repos/dist/dev/arrow/apache-arrow-nanoarrow-0.7.0-rc1/
>> > > > > [4]
>> > > > >
>> > > >
>> > >
>> >
>> https://github.com/apache/arrow-nanoarrow/blob/apache-arrow-nanoarrow-0.7.0-rc1/CHANGELOG.md
>> > > > > [5]
>> > > > >
>> > > >
>> > >
>> >
>> https://github.com/apache/arrow-nanoarrow/blob/main/dev/release/README.md
>> > > >
>> > >
>> >
>>
>

Reply via email to