My vote is +1, the vote is closed.

The vote passes with 5 binding +1 votes and 1 non-binding +1 vote.

Binding +1:
Matt
Bryce
Ian
David
Raul

Non-binding +1:
Pedro

Thanks everyone! I'll go do the release now.

--Matt

On Tue, Apr 28, 2026 at 3:53 AM Raúl Cumplido <[email protected]> wrote:
>
> +1 (binding)
>
> I am still facing the same issue with the sanitizers on Debian Forky
> as with previous releases. Sanitizers on go with glibc2.42 fail.
>
> Apart from the sanitizer issue the rest of the tests and build were
> successful on Debian 14. With Go 1.26.2
>
> I've also fully verified on Ubuntu 24.04.
>
> Thanks Matt for the release!
>
> El mar, 28 abr 2026 a las 1:03, David Li (<[email protected]>) escribió:
> >
> > +1 (Go 1.26, Ubuntu 25.04, AMD64)
> >
> > On Tue, Apr 28, 2026, at 04:53, Ian Cook wrote:
> > > +1
> > >
> > > I successfully ran `dev/release/verify_rc.sh 18.6.0 0` on macOS 26.3.1 on
> > > Apple M3.
> > >
> > > The validation script printed some linker warnings, but I believe these 
> > > are
> > > innocuous:
> > >
> > > ld: warning:
> > > '/private/var/folders/t6/m8h3x91n7ll5rcx_jq4rk41m0000gn/T/go-link-1905812641/000021.o'
> > > has malformed LC_DYSYMTAB, expected 98 undefined symbols to start at
> > > index
> > > 1626, found 95 undefined symbols starting at index 1626
> > >
> > > Ian
> > >
> > > On Sat, Apr 25, 2026 at 1:08 PM Pedro Matias <[email protected]>
> > > wrote:
> > >
> > >> Thanks for making the PR for the issue, I didn't have time yesterday.
> > >> +1 from me (non binding), macOS 15.5 ARM CPU (M4 Max).
> > >>
> > >> On Fri, Apr 24, 2026 at 5:43 PM Bryce Mecum <[email protected]> wrote:
> > >>
> > >> > I agree, no need for a new RC.
> > >> >
> > >> > On Fri, Apr 24, 2026 at 9:15 AM Matt Topol <[email protected]>
> > >> wrote:
> > >> > >
> > >> > > Good catch! I've created https://github.com/apache/arrow-go/pull/781
> > >> > > to address the issue with downloading the KEYS file. I don't
> > >> > > necessarily think this needs to block the release but will cut a new
> > >> > > RC if you guys think that would be appropriate here.
> > >> > >
> > >> > > --Matt
> > >> > >
> > >> > > On Thu, Apr 23, 2026 at 12:47 PM Bryce Mecum <[email protected]>
> > >> > wrote:
> > >> > > >
> > >> > > > +1
> > >> > > >
> > >> > > > I ran `dev/release/verify_rc.sh 18.6.0 0` on macOS 26.3.1 
> > >> > > > (aarch64).
> > >> I
> > >> > > > had to work around the issue Pedro mentions in this thread.
> > >> > > >
> > >> > > > On Wed, Apr 22, 2026 at 3:42 PM Matt Topol <[email protected]>
> > >> > wrote:
> > >> > > > >
> > >> > > > > Hi,
> > >> > > > >
> > >> > > > > I would like to propose the following release candidate (RC0) of
> > >> > > > > Apache Arrow Go version 18.6.0.
> > >> > > > >
> > >> > > > > This release candidate is based on commit:
> > >> > > > > 7d825c02571af354a3047d55e33aae95b08f975c [1]
> > >> > > > >
> > >> > > > > The source release rc0 is hosted at [2].
> > >> > > > >
> > >> > > > > This is not a permanent URL. If the RC is accepted, it will be
> > >> moved
> > >> > to
> > >> > > > > the final release location. The SHA512 hash of the source tarball
> > >> is:
> > >> > > > >
> > >> >
> > >> a536e3a57b45fb4fdd7f90aa58ef0a999d51f8fbf560a177a8842e792298ee6cd05e0fb068ce61cc071d9bb8069114b7010480b1a71f6dfbf5dafe30a433c070.
> > >> > > > >
> > >> > > > > Please download, verify checksums and signatures, run the unit
> > >> tests,
> > >> > > > > and vote on the release. See [3] for how to validate a release
> > >> > candidate.
> > >> > > > >
> > >> > > > > The vote will be open for at least 72 hours.
> > >> > > > >
> > >> > > > > [ ] +1 Release this as Apache Arrow Go 18.6.0
> > >> > > > > [ ] +0
> > >> > > > > [ ] -1 Do not release this as Apache Arrow Go 18.6.0 because...
> > >> > > > >
> > >> > > > > --Matt
> > >> > > > >
> > >> > > > > [1]:
> > >> >
> > >> https://github.com/apache/arrow-go/tree/7d825c02571af354a3047d55e33aae95b08f975c
> > >> > > > > [2]: https://github.com/apache/arrow-go/releases/v18.6.0-rc0
> > >> > > > > [3]:
> > >> >
> > >> https://github.com/apache/arrow-go/blob/main/dev/release/README.md#verify
> > >> >
> > >>

Reply via email to