Thanks for the suggestion, Sebb. I went ahead and moved the original SHA into 
.sha file and re-generated the SHA1 into the .sha1 file. 

@Alan, @sebb, would either of you mind verifying the modified files?

I will follow-up separately with other folks who did their +1's to re-check the 
files.

thanks
-- Hitesh

On Feb 28, 2014, at 12:32 PM, sebb wrote:

> On 28 February 2014 19:48, Alan Gates <ga...@hortonworks.com> wrote:
>> +1
>> 
>> One note is that the signatures given say sha1, but you actually have use 
>> openssl sha to get the same values.  If you do sha1sum (which was my first 
>> assumption anyway) you get a different non-matching values.  You might want 
>> to change the filename to "tez-0.3.0-incubating.tar.gz.sha"
> 
> Or better, use SHA-1 rather than SHA (aka SHA-0) which is relatively
> weak and not well supported by tools.
> 
> I think it would be OK just to replace the sha1 file contents with the
> appropriate SHA-1 hash.
> No need to respin the release, as it that has not changed, but it
> would make sense to get a few people to check the updated hash works
> for them.
> 
> If you leave the sha1 file with SHA-0 contents, that is potentially
> going to cause problems for downloaders; they won't be expecting a
> SHA-0 hash in that file.
> 
>> Other than that, checked the signatures, looked at LICENSE, NOTICE, 
>> DISCLAIMER, built and ran the unit tests.  All looks good.
>> 
>> Alan.
>> 
>> On Feb 28, 2014, at 11:28 AM, Mahadev Konar <maha...@hortonworks.com> wrote:
>> 
>>> +1 (binding)
>>> 
>>> - verified signatures and ran some sample test jobs.
>>> 
>>> 
>>> 
>>> Mahadev Konar
>>> Hortonworks Inc.
>>> http://hortonworks.com/
>>> 
>>> 
>>> On Fri, Feb 28, 2014 at 8:05 AM, Jason Lowe <jl...@yahoo-inc.com> wrote:
>>>> +1 (non-binding)
>>>> 
>>>> - Verified signatures
>>>> - Built from source, installed on single-node cluster
>>>> - Ran  some sample Tez jobs
>>>> 
>>>> Jason
>>>> 
>>>> 
>>>> On 02/25/2014 06:28 PM, Hitesh Shah wrote:
>>>>> 
>>>>> Hello folks,
>>>>> 
>>>>> I have created a tez-0.3.0-incubating release candidate (rc1). This is the
>>>>> second release for Tez.
>>>>> 
>>>>> The previous RC was cancelled due to a bug discovered when the RC was
>>>>> tested against downstream projects.
>>>>> 
>>>>> GIT source tag:
>>>>> https://git-wip-us.apache.org/repos/asf/incubator-tez/repo?p=incubator-tez.git;a=log;h=refs/tags/release-0.3.0-incubating-rc1
>>>>> ( commit hash 6987e18f6b3c5358e1eb125bc2d63be39f71e892 )
>>>>> Staging site:
>>>>> https://dist.apache.org/repos/dist/dev/incubator/tez/0.3.0-incubating-rc1/
>>>>>  (
>>>>> svn revision 4508 )
>>>>> Nexus Staging URL:
>>>>> https://repository.apache.org/content/repositories/orgapachetez-1003
>>>>> 
>>>>> PGP release keys:
>>>>> http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xA9510905F0B000F0
>>>>> KEYS file also available at
>>>>> https://dist.apache.org/repos/dist/release/incubator/tez/KEYS
>>>>> 
>>>>> One can look into the issues fixed in this release at:
>>>>> https://issues.apache.org/jira/browse/TEZ/fixforversion/12325655 or look 
>>>>> at
>>>>> the CHANGES.txt in the release tarball.
>>>>> 
>>>>> Vote will be open for at least 72 hours ( until the required number of
>>>>> IPMC votes are obtained ).
>>>>> 
>>>>> [ ] +1 approve
>>>>> [ ] +0 no opinion
>>>>> [ ] -1 disapprove (and reason why)
>>>>> 
>>>>> For folks not familiar with vetting a release, please refer to
>>>>> http://incubator.apache.org/guides/releasemanagement.html#check-list
>>>>> 
>>>>> thanks
>>>>> -- Hitesh
>>>> 
>>>> 
>>>> 
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>>> 
>>> 
>>> --
>>> 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.
>>> 
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>> 
>> 
>> 
>> --
>> 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.
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Reply via email to