+1 (binding)

* Verified signature and checksum
* Ran Java unit tests, packaged to JARs
* Build and run C++ unit tests on Ubuntu 14.04 / gcc 4.8
* Built Parquet C++ against Arrow 0.5.0 and ran its unit tests
* Ran Python unit tests including --with-parquet
* Ran GLib C Ruby unit tests
* Ran integration tests (after manually re-enabling the Java tester
class per Bryan's note, I don't think this is a blocker)

* Ran C++ unit tests for Arrow, Parquet tests against Arrow 0.5.0, and
Python tests with Visual Studio 2017

- Wes

On Thu, Jul 20, 2017 at 7:36 PM, Bryan Cutler <cutl...@gmail.com> wrote:
> I ran tests for Java, C++, Python
> Integration tests had Java disabled, not sure if that would be a blocker or
> not.  After re-enabling, all tests pass.  Here is the PR to re-enable
> https://github.com/apache/arrow/pull/875
>
> +0 (non-binding) since I'm not sure if the above is a blocker
>
> On Thu, Jul 20, 2017 at 10:17 AM, Wes McKinney <wesmck...@gmail.com> wrote:
>
>> Hello all,
>>
>> I'd like to propose the 2nd release candidate (rc2) of Apache Arrow version
>> 0.5.0.  This is a major release consisting of 130 resolved JIRAs [1].
>>
>> The source release rc2 is hosted at [2]. It is the same as the rc1
>> release with the omission of the cpp/src/plasma directory, pending IP
>> clearance.
>>
>> This release candidate is based on commit
>> e9f76e125b836d0fdc0a533e2fee3fca8bf4c1a1 [3]
>>
>> The will be open for ~72 hours, ending 17:30 UTC Time on Sunday
>> July 23, 2017.
>>
>> [ ] +1 Release this as Apache Arrow 0.5.0
>> [ ] +0
>> [ ] -1 Do not release this as Apache Arrow 0.5.0 because...
>>
>> 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.5.0
>> [2]: https://dist.apache.org/repos/dist/dev/arrow/apache-arrow-0.5.0-rc2/
>> [3]: https://github.com/apache/arrow/commit/e9f76e125b836d0fdc0a533e2fee3f
>> ca8bf4c1a1
>>

Reply via email to