or Plasma.
>
>
> Thanks,
> --
> kou
>
> In
> "[VOTE] Release Apache Arrow 0.8.0 RC2" on Tue, 12 Dec 2017 17:33:50 -0500,
> Wes McKinney wrote:
>
>> Hello all,
>>
>> I'd like to propose the 2nd release candidate (rc2) of Apache
>
++'s unit tests was failed only once but I couldn't
reproduce it... It don't remember the failed test but it
may be client_tests for Plasma.
Thanks,
--
kou
In
"[VOTE] Release Apache Arrow 0.8.0 RC2" on Tue, 12 Dec 2017 17:33:50 -0500,
Wes McKinney wrote:
> Hello a
+1
Verified signatures and checksums
Ran unit tests for arrow python and c++ using clang on Arch Linux as well
as parquet-cpp unit tests.
On Sat, Dec 16, 2017, 00:25 Jacques Nadeau wrote:
> Sounds good.
>
> +1 (binding)
>
> On Dec 15, 2017 7:05 PM, "Wes McKinney" wrote:
>
> > Since Ray has been
Sounds good.
+1 (binding)
On Dec 15, 2017 7:05 PM, "Wes McKinney" wrote:
> Since Ray has been running on builds of trunk I don’t think we should delay
> the release on account of it. We should consider doing a 0.8.1 within
> reasonably short order and see that Ray is working well with that RC.
Since Ray has been running on builds of trunk I don’t think we should delay
the release on account of it. We should consider doing a 0.8.1 within
reasonably short order and see that Ray is working well with that RC.
On Fri, Dec 15, 2017 at 6:03 PM Jacques Nadeau wrote:
> I ran the release valida
I ran the release validation and things look good. However, what do other
people think about ARROW-1924? I didn't see any feedback on Philipp's
comments here.
On Thu, Dec 14, 2017 at 12:24 AM, Uwe L. Korn wrote:
> +1 (binding)
>
> * Ran verify-release-candidate.sh on macOS; verified signature,
>
+1 (binding)
* Ran verify-release-candidate.sh on macOS; verified signature,
checksums, test for Java, Python, C++, C/GLib, Java/C++ integration, JS
Uwe
On Thu, Dec 14, 2017, at 01:01 AM, Philipp Moritz wrote:
> On Ray we are currently blocked from using the 0.8 release candidate by
> this issue
On Ray we are currently blocked from using the 0.8 release candidate by
this issue: https://issues.apache.org/jira/browse/ARROW-1924
If we don't want to delay the release for longer releasing that's fine with
us because we are tracking specific arrow commits and ship these versions
of pyarrow with
+1
Built and ran tests for C++, Python, Java (Ubuntu 16.04, gcc 5.4,
openjdk-1.8)
Ran integration tests
Verified signature and checksum
Tested downstream with Spark
On Tue, Dec 12, 2017 at 2:50 PM, Wes McKinney wrote:
> +1 (binding)
>
> * Ran verify-release-candidate.sh on Linux (Ubuntu 14.04,
+1 (binding)
* Ran verify-release-candidate.sh on Linux (Ubuntu 14.04, gcc 4.8) --
verified signature, checksums, test for Java, Python, C++, C/GLib,
Java/C++ integration, JS
* Ran verify-release-candidate.bat on Visual Studio 2017 (C++ unit
tests, Python unit tests, Parquet integration)
Thanks
Hello all,
I'd like to propose the 2nd release candidate (rc2) of Apache
Arrow version 0.8.0 (rc0 was cancelled, I cut but then aborted rc1
upon encountering ARROW-1917). This is a
major release consisting of 286 resolved JIRAs [1].
The source release rc2 is hosted at [2].
This release candidate
11 matches
Mail list logo