+1

* Verified signatures and hashes
* built from source
* ran through examples - both DSL and curl


On Wed, Nov 13, 2013 at 10:14 AM, Kevin Minder <[email protected]
> wrote:

> +1
>
> 1) Downloaded all RC artifacts and checked md5, sha hashes and asc
> signatures.
> 2) Extracted the src package and ran 'ant verify' successfully.
> 3) Extracted the binary zip package and ran/verified all the
> sample/Example*.groovy scripts against Sandbox 2.0 GA.
>
> Note: I did have to restart HBase but this is expected and is different
> from the error found in RC2.
>
>
> On 11/12/13 4:00 PM, larry mccay wrote:
>
>> Hi Everyone,
>>
>>    A candidate for the Apache Knox (Incubator) 0.3.1 release is
>> available
>>
>>     at:
>> https://dist.apache.org/repos/dist/dev/incubator/knox/knox-
>> incubating-0.3.1/
>>
>> The release candidate is a zip archive of the sources in:
>>
>> https://git-wip-us.apache.org/repos/asf/incubator-knox.git
>> Branch v0.3.1 (git checkout -b v0.3.1)
>>
>> The SHA1 checksum of the archive
>> is 04bb11360f57c0431c30cfb181e3199868fe6053.
>>
>> Please vote on releasing this package as Apache Knox (Incubator) 0.3.1.
>>
>> The vote is open for the next 72 hours and passes if a majority
>> of at least three +1 Apache Knox (Incubator) PMC votes are cast.
>>
>> We have two bug fixes in this patch release candidate:
>>
>> One fix is for an issue (KNOX-188) that would adversely affect a load
>> balanced cluster of Knox Gateway instances and therefore an issue
>> for HA deployment scenarios.
>>
>> The other is for a ClientDSL HBase issue (KNOX-199).
>>
>> There are no known outstanding functional issues. Please test as
>> much as possible within this 72 hour period and cast your vote.
>>    [ ] +1 Release this package as Apache Knox (Incubator) 0.3.1
>>    [ ] -1 Do not release this package because...
>>
>> Thanks!
>>
>> --larry
>>
>>
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity
> to which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>

Reply via email to