Checked license, notice, checksums, signature. Built on OS X under JDK 1.8.

I got “gpg: Can’t check signature: public key not found” when I tried to 
verify. I tried importing 
<>, but not the right key, 

 <>In my opinion, the README 
should contain build instructions (or pointers to them). And Java build 
instructions should say which JDKs are supported.

It would also be nice if there were release notes.

Failures & errors in the java tests:

Failed tests: 
  TestComplexWriter.listListType:186 record: 3 expected:<0> but was:<2>
  TestValueVector.testNullableInt:268 expected:<3> but was:<1>

Tests in error: 
  TestComplexWriter.promotableWriter:294 NullPointer
  TestComplexWriter.simpleUnion:255 NullPointer
  TestComplexWriter.unionListListType:225 NullPointer
  TestComplexWriter.listScalarType:124 NullPointer
  TestComplexWriter.listMapType:153 NullPointer
  TestComplexWriter.simpleNestedTypes:68 NullPointer

Tests run: 34, Failures: 2, Errors: 6, Skipped: 0

I tried to build C++ in release mode. I had to `brew install cmake`. Then I got 
the following error:

CMake Error at 
  Unable to find the requested Boost libraries.

  Unable to find the Boost header files.  Please set BOOST_ROOT to the root
  directory containing Boost or BOOST_INCLUDEDIR to the directory containing
  Boost's headers.

I didn’t try the python build.


> On Sep 19, 2016, at 3:09 PM, Julien Le Dem <> wrote:
> Hi all,
> I have published a release candidate for arrow-0.1.0 RC0
> I don't think it is ready for a vote yet but I wanted to test the
> publication process:
> The RC0 is here:
> I also have staged maven artifacts (password protected):
> Obviously we don't want to release those artifacts until the rc is voted on.
> to build from source you can independently build java/cpp/python.
> for java:
> cd java
> mvn install
> for cpp and python follow their respective README int he eponymous folders.
> I had to generate a new private key so it is not signed yet by others. I
> can check in my public key in the arrow repo.
> Julien
> -- 
> Julien

Reply via email to