1. Verify the signature: OK
2. Verify the checksum: OK
3. Untar the archive tarball: OK
4. Run RAT checks to validate license headers: RAT checks passed
5. Build and test the project: all unit tests passed.

+1 (non-binding)

I did see that my build took >12 minutes and used all 100% of all 8 cores &
32GB of memory (openjdk-8 ubuntu 18.04) which I haven't noticed before.
On Fri, Jul 10, 2020 at 4:37 AM OpenInx <open...@gmail.com> wrote:

> I followed the verify guide here (
> https://lists.apache.org/thread.html/rd5e6b1656ac80252a9a7d473b36b6227da91d07d86d4ba4bee10df66%40%3Cdev.iceberg.apache.org%3E)
> :
>
> 1. Verify the signature: OK
> 2. Verify the checksum: OK
> 3. Untar the archive tarball: OK
> 4. Run RAT checks to validate license headers: RAT checks passed
> 5. Build and test the project: all unit tests passed.
>
> +1 (non-binding).
>
> On Fri, Jul 10, 2020 at 9:46 AM Ryan Blue <rb...@netflix.com.invalid>
> wrote:
>
>> Hi everyone,
>>
>> I propose the following RC to be released as the official Apache Iceberg
>> 0.9.0 release.
>>
>> The commit id is 4e66b4c10603e762129bc398146e02d21689e6dd
>> * This corresponds to the tag: apache-iceberg-0.9.0-rc5
>> * https://github.com/apache/iceberg/commits/apache-iceberg-0.9.0-rc5
>> * https://github.com/apache/iceberg/tree/4e66b4c1
>>
>> The release tarball, signature, and checksums are here:
>> *
>> https://dist.apache.org/repos/dist/dev/iceberg/apache-iceberg-0.9.0-rc5/
>>
>> You can find the KEYS file here:
>> * https://dist.apache.org/repos/dist/dev/iceberg/KEYS
>>
>> Convenience binary artifacts are staged in Nexus. The Maven repository
>> URL is:
>> *
>> https://repository.apache.org/content/repositories/orgapacheiceberg-1008/
>>
>> This release includes support for Spark 3 and vectorized reads for flat
>> schemas in Spark.
>>
>> Please download, verify, and test.
>>
>> Please vote in the next 72 hours.
>>
>> [ ] +1 Release this as Apache Iceberg 0.9.0
>> [ ] +0
>> [ ] -1 Do not release this because...
>>
>> --
>> Ryan Blue
>> Software Engineer
>> Netflix
>>
>

Reply via email to