> However I am seeing ACCUMULO-3545[1] that
I need to investigate.

Ok. I'll cut another RC as soon as that's complete.

On Thu, Jan 29, 2015 at 6:03 PM, Josh Elser <josh.el...@gmail.com> wrote:

> Given the stuff Keith found already, I'm -1, but I did take some time this
> RC to rerun some tests. I had one IT that failed on me from the source
> build which we can fix later -- things are looking good otherwise from my
> testing.
>
> Thanks for working through this Corey, and Keith for finding bugs :)
>
>
> Corey Nolet wrote:
>
>>    Devs,
>>
>>      Please consider the following candidate for Apache Accumulo 1.6.2
>>
>>      Branch: 1.6.2-rc3
>>      SHA1: 3a6987470c1e5090a2ca159614a80f0fa50393bf
>>      Staging Repository:
>> https://repository.apache.org/content/repositories/
>> orgapacheaccumulo-1021/
>>
>>      Source tarball:
>> https://repository.apache.org/content/repositories/
>> orgapacheaccumulo-1021/org/apache/accumulo/accumulo/1.6.
>> 2/accumulo-1.6.2-src.tar.gz
>>      Binary tarball:
>> https://repository.apache.org/content/repositories/
>> orgapacheaccumulo-1021/org/apache/accumulo/accumulo/1.6.
>> 2/accumulo-1.6.2-bin.tar.gz
>>      (Append ".sha1", ".md5" or ".asc" to download the signature/hash for
>> a
>> given artifact.)
>>
>>      Signing keys available at: https://www.apache.org/dist/accumulo/KEYS
>>
>>      Over 1.6.1, we have 148 issues resolved:
>> https://git-wip-us.apache.org/repos/asf?p=accumulo.git;a=
>> blob_plain;f=CHANGES;hb=1.6.2-rc3
>>
>>      Testing: All unit, integration and functional tests are passing.
>>
>>      API compatibility report for 1.6.1 to 1.6.2:
>> http://people.apache.org/~cjnolet/accumulo-1.6.2-rc3/
>> compat_reports/accumulo/1.6.1_to_1.6.2/compat_report.html
>>
>>      API backwards compatibility report for 1.6.2 to 1.6.1:
>> http://people.apache.org/~cjnolet/accumulo-1.6.2-rc3/
>> compat_reports/accumulo/1.6.2_to_1.6.1/compat_report.html
>>
>>      The vote will be open until Saturday, January 31st 12:00AM UTC (1/30
>> 8:00PM ET, 1/30 5:00PM PT)
>>
>>

Reply via email to