+1

The verification process was very heavy weight (running TPCH, etc) and I
didn't let it complete. -- I wonder if we really need to run the full test
suites as part of doing so

    Finished release [optimized] target(s) in 27m 55s

The changelog shows a very impressive list of features. Well done

Andrew

On Mon, Oct 24, 2022 at 2:11 AM Daniël Heres <danielhe...@gmail.com> wrote:

> +1 (binding)
>
> Thanks for this exciting release!
>
> Best regards,
>
> Daniël Heres
>
> Op zo 23 okt. 2022 om 22:06 schreef Andy Grove <andygrov...@gmail.com>:
>
> > Hi,
> >
> > I would like to propose a release of Apache Arrow Ballista
> Implementation,
> > version 0.9.0.
> >
> > This release candidate is based on commit:
> > 018b542716de13838ad1e2f803d38e47355183af [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. The vote will be open for at least 72 hours.
> >
> > Only votes from PMC members are binding, but all members of the community
> > are
> > encouraged to test the release and vote with "(non-binding)".
> >
> > The standard verification procedure is documented at
> >
> >
> https://github.com/apache/arrow-ballista/blob/master/dev/release/README.md#verifying-release-candidates
> > .
> >
> > [ ] +1 Release this as Apache Arrow Ballista 0.9.0
> > [ ] +0
> > [ ] -1 Do not release this as Apache Arrow Ballista 0.9.0 because...
> >
> > *NOTES:*
> > *- This is rc1 because I ran into an issue with rc1*
> > *- The verification test will run integration tests and requires Docker
> > Compose version 3.3 or later to be installed*
> >
> > [1]:
> >
> >
> https://github.com/apache/arrow-ballista/tree/018b542716de13838ad1e2f803d38e47355183af
> > [2]:
> >
> >
> https://dist.apache.org/repos/dist/dev/arrow/apache-arrow-ballista-0.9.0-rc2
> > [3]:
> >
> >
> https://github.com/apache/arrow-ballista/blob/018b542716de13838ad1e2f803d38e47355183af/CHANGELOG.md
> >
>
>
> --
> Daniël Heres
>

Reply via email to