+1

I ran the verification script, looked at changelog, and the commits. Thanks
Neville for driving this process

Andrew

On Mon, Feb 21, 2022 at 7:55 AM Chao Sun <sunc...@apache.org> wrote:

> +1 (non-binding)
>
> Verified on macos with `dev/release/verify-release-candidate.sh` and it
> looks good.
>
> On Sun, Feb 20, 2022 at 1:06 PM Sutou Kouhei <k...@clear-code.com> wrote:
>
> > Hi,
> >
> > Great!
> > Could you also add your PGP key to
> > https://dist.apache.org/repos/dist/release/arrow/KEYS
> > ?
> >
> > The release/arrow/KEYS content is distributed as
> > https://downloads.apache.org/arrow/KEYS .
> >
> >
> > Thanks,
> > --
> > kou
> >
> > In <cabgzuegyc3-trrvucmtfnxgpkbp3io2nq6swof2umq2f3ka...@mail.gmail.com>
> >   "Re: [VOTE][RUST] Release Apache Arrow Rust 9.1.0 RC1" on Sun, 20 Feb
> > 2022 10:43:16 +0200,
> >   Neville Dipale <nevilled...@gmail.com> wrote:
> >
> > > Hi Kou,
> > >
> > > Thanks, I've just managed to add my key through some fiddling before I
> > saw
> > > your email. My RC verification is still running :)
> > >
> > > Also added it to the Ubuntu keyserver if it helps.
> > >
> > > On Sun, 20 Feb 2022 at 06:34, Sutou Kouhei <k...@clear-code.com> wrote:
> > >
> > >> Hi,
> > >>
> > >> It seems that Neville forgot to add Neville's PGP key to
> > >>
> > >>   * https://dist.apache.org/repos/dist/dev/arrow/KEYS
> > >>   * https://dist.apache.org/repos/dist/release/arrow/KEYS
> > >>
> > >> See the header comment of them how to add a PGP key.
> > >>
> > >> Committers can update them by Subversion client with their
> > >> ASF account. e.g.:
> > >>
> > >>   $ svn co https://dist.apache.org/repos/dist/dev/arrow
> > >>   $ cd arrow
> > >>   $ editor KEYS
> > >>   $ svn ci KEYS
> > >>
> > >> If Neville doesn't have a PGP key,
> > >> https://infra.apache.org/release-signing.html#generate may
> > >> be helpful.
> > >>
> > >>
> > >> Thanks,
> > >> --
> > >> kou
> > >>
> > >> In <CAJEf=X4qBM5smfiDGCVC=
> pnp3cu91r5vf_6szh1z4uab_qp...@mail.gmail.com>
> > >>   "Re: [VOTE][RUST] Release Apache Arrow Rust 9.1.0 RC1" on Sat, 19
> Feb
> > >> 2022 11:52:44 -0700,
> > >>   Andy Grove <andygrov...@gmail.com> wrote:
> > >>
> > >> > I'm using the same process as usual (as far as I am aware) and the
> > script
> > >> > failed with:
> > >> >
> > >> > gpg: Signature made Sat 19 Feb 2022 10:01:41 AM MST
> > >> > gpg:                using EDDSA key
> > >> 3905F254F9E504B40FFF6CF6000488D7717D3FB2
> > >> > gpg: Can't check signature: No public key
> > >> > + cleanup
> > >> > + '[' no = yes ']'
> > >> > + echo 'Failed to verify release candidate. See
> /tmp/arrow-9.1.0.62KW4
> > >> for
> > >> > details.'
> > >> >
> > >> >
> > >> > On Sat, Feb 19, 2022 at 10:04 AM Neville Dipale <
> > nevilled...@gmail.com>
> > >> > wrote:
> > >> >
> > >> >> Hi,
> > >> >>
> > >> >> I would like to propose a release of Apache Arrow Rust
> > Implementation,
> > >> >> version 9.1.0.
> > >> >>
> > >> >> This release candidate is based on commit:
> > >> >> ecba7dc0830dbde6aa6dd9432519b776e40c1e85 [1]
> > >> >>
> > >> >> The proposed release tarball and signatures are hosted at [2].
> > >> >>
> > >> >> The changelog is located at [3].
> > >> >>
> > >> >> Please download, verify checksums and signatures, run the unit
> tests,
> > >> >> and vote on the release. There is a script [4] that automates some
> of
> > >> >> the verification.
> > >> >>
> > >> >> The vote will be open for at least 72 hours.
> > >> >>
> > >> >> [ ] +1 Release this as Apache Arrow Rust
> > >> >> [ ] +0
> > >> >> [ ] -1 Do not release this as Apache Arrow Rust  because...
> > >> >>
> > >> >> [1]:
> > >> >>
> > >> >>
> > >>
> >
> https://github.com/apache/arrow-rs/tree/ecba7dc0830dbde6aa6dd9432519b776e40c1e85
> > >> >> [2]:
> > >> >>
> > https://dist.apache.org/repos/dist/dev/arrow/apache-arrow-rs-9.1.0-rc1
> > >> >> [3]:
> > >> >>
> > >> >>
> > >>
> >
> https://github.com/apache/arrow-rs/blob/ecba7dc0830dbde6aa6dd9432519b776e40c1e85/CHANGELOG.md
> > >> >> [4]:
> > >> >>
> > >> >>
> > >>
> >
> https://github.com/apache/arrow-rs/blob/master/dev/release/verify-release-candidate.sh
> > >> >>
> > >>
> >
>

Reply via email to