arrow-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uwe L. Korn" <uw...@xhochy.com>
Subject Re: [VOTE] Release Apache Arrow 0.3.0 - rc1
Date Wed, 03 May 2017 08:27:41 GMT
+1 (binding)

I did check the following:
- Build and tested C++ on Linux and macOS
- Build and tested Java on Linux and macOS
- Build and tested Python Linux and macOS with pandas 0.19 and pandas
0.20.
(This failed for Pandas 0.18:
https://issues.apache.org/jira/browse/ARROW-944 but I don't think this a
blocker)
Build Glib on Linux

On Wed, May 3, 2017, at 12:39 AM, Bryan Cutler wrote:
> +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>*
> > >
> >

Mime
View raw message