Mailing-List: contact dev-help@arrow.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@arrow.apache.org
MIME-Version: 1.0
In-Reply-To: <CAJPUwMDPe=AoMad4SUoZn3c4gxH7e=8wNg6SEYYVK=c1msMAHw@mail.gmail.com>
References: <CAJPUwMBosGUe8VoAKF+r4L9ZLroEDN3HkT7GATT5HQfwobNCAg@mail.gmail.com>
 <CAJPUwMDPe=AoMad4SUoZn3c4gxH7e=8wNg6SEYYVK=c1msMAHw@mail.gmail.com>
From: Bryan Cutler <cutlerb@gmail.com>
Date: Tue, 2 May 2017 15:39:55 -0700
Message-ID: <CABr4ZASBKbe=dokE9JmjzNsr2ixDp3pL26W_y6zkbH_oKp2pTQ@mail.gmail.com>
Subject: Re: [VOTE] Release Apache Arrow 0.3.0 - rc1
To: dev@arrow.apache.org
Content-Type: multipart/alternative; boundary=001a114ac87412d689054e923817
archived-at: Tue, 02 May 2017 22:40:02 -0000

--001a114ac87412d689054e923817
Content-Type: text/plain; charset=UTF-8

+1 (non-binding)

* Build Java with OpenJDK version "1.8.0_121" and ran unit tests
* Build C++ and Python with gcc version 5.4.0 20160609 (Ubuntu
5.4.0-6ubuntu1~16.04.4) and ran unit tests for both
* Ran Integration tests
* Tested with SPARK-13534

On Tue, May 2, 2017 at 1:47 PM, Wes McKinney <wesmckinn@gmail.com> wrote:

> Addition to the list of checks: my C++/Python builds on Linux included
> building parquet-cpp master against the Arrow 0.3-rc1 tarball and
> building/testing the Python-Parquet adapter
>
> On Tue, May 2, 2017 at 4:46 PM, Wes McKinney <wesmckinn@gmail.com> wrote:
>
> > Hello all,
> >
> > I'd like to propose the 2nd release candidate (rc1) of Apache Arrow
> version
> > 0.3.0.  It covers a total of 263 resolved JIRAs [1] Thanks to everyone
> who
> > contributed to this release.
> >
> > The source release rc1 is hosted at [2].
> > This release candidate is based on commit
> > d8db8f8a11abbbb6c45645b2d7370610311731bd located at [3].
> >
> > The vote will be open for the next ~72 hours ending at 16:45 Eastern US
> > Time,
> > May 5, 2017.
> >
> > [ ] +1
> > [ ] +0
> > [ ] -1
> >
> > I have
> >
> > * Built Java libraries and run unit tests
> > * Built and installed C++ and Python libraries on Ubuntu 14.04 (gcc 4.8),
> > and
> >   run unit tests
> > * Built and installed C++ and Python libraries on Visual Studio 2015, and
> > run
> >   unit tests
> > * Run the Java<->C++ integration tests for the stream and file formats
> > * Build and installed C GLib bindings. The tarball does not include the
> > test
> >   suite; it would be good to provide a way to validate the build from a
> > source
> >   release
> >
> > Here's my vote: +1 (binding)
> >
> > Thanks,
> > Wes
> >
> > How to validate a release signature:
> > https://httpd.apache.org/dev/verification.html
> >
> > [1]:
> > https://issues.apache.org/jira/issues/?jql=project%20%
> > 3D%20ARROW%20AND%20status%20in%20(Resolved%2C%20Closed)%
> > 20AND%20fixVersion%20%3D%200.3.0
> > [2] *https://dist.apache.org/repos/dist/dev/arrow/apache-
> arrow-0.3.0-rc1/
> > <https://dist.apache.org/repos/dist/dev/arrow/apache-arrow-0.3.0-rc1/>*
> > [3]
> > *https://github.com/apache/arrow/tree/d8db8f8a11abbbb6c45645b2d73706
> > 10311731bd
> > <https://github.com/apache/arrow/tree/d8db8f8a11abbbb6c45645b2d73706
> > 10311731bd>*
> >
>

--001a114ac87412d689054e923817--