+1.

Apart from LuaJIT and the regression stuff (which is ignored, right?),
only one file is missing a license header,
"plugins/experimental/collapsed_connection/MurmurHash3.h"

Other than that:

- License and Notice in place
- No bad licenses found
- Sigs match, digests match
- It builds \o/

For the nitty gritty details, see
http://compliance.rocks/result.html?23e9661f

With regards,
Daniel.

On 09/08/2015 08:24 PM, Bryan Call wrote:
> +1 - Checked signatures and ran regression on Fedora 22.
> 
> -Bryan
> 
>> On Sep 4, 2015, at 9:08 AM, Phil Sorber <sor...@apache.org> wrote:
>>
>> Hello All,
>>
>> I've prepared a release for v5.3.2 (RC0) which is the latest stable release
>> in the 5.3.x series. This is the third release in our Long Term Support
>> (LTS) version as detailed in our Release Management document:
>>
>> https://cwiki.apache.org/confluence/display/TS/Release+Management
>>
>> Changes since 5.3.1:
>>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12327093&styleName=Text&projectId=12310963
>>
>> A summary of the new features in 5.3.x are here:
>>
>> https://cwiki.apache.org/confluence/display/TS/What%27s+new+in+v5.3.x
>>
>> Information about upgrading to this release from previous ones is available
>> at:
>>
>> https://cwiki.apache.org/confluence/display/TS/Upgrading+to+v5.0
>>
>> The cache in this release is compatible with the previous 5.x and 4.x
>> releases.
>>
>> The artifacts are available for download at:
>>
>> http://people.apache.org/~sorber/releases/trafficserver/5.3.2-rc0/
>>
>> MD5: c62745afdb0f39a7631eb553b6f18a26
>> SHA1: b496323cc95b90bfbb4df6e7432e3df0b8a1671c
>>
>> This corresponds to git:
>>
>> Hash: fc18910a857912d0290a04013eefa4edbb0d6cdd
>> Tag: 5.3.2-rc0
>>
>> Which can be verified with the following:
>>
>> git tag -v 5.3.2-rc0
>>
>> My code signing key is available here:
>>
>> http://people.apache.org/~sorber/gpg-code-signing-key.asc
>>
>> Make sure you refresh from a key server to get all relevant signatures.
>>
>> The vote is open until Saturday Sept 12th, 2015.
>>
>> Thanks All!
> 

Reply via email to