chukwa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eric Yang <ey...@yahoo-inc.com>
Subject Re: release tarball
Date Thu, 02 Jul 2009 20:20:10 GMT
Paste your public key in KEYS, and run:

gpg --armor --output chukwa-0.2.0.tar.gz.asc --detach-sig
chukwa-0.2.0.tar.gz.

This should sign the release.

Regards,
Eric

On 7/2/09 1:04 PM, "Ariel Rabkin" <asrabkin@gmail.com> wrote:

> *nod*, that's what I figured. The copy on my people.apache.org page
> (see first email) was signed with my personal key.  But I'm not quite
> sure what to do next with the key.  I figure I need to put it
> somewhere, and need someone to sign it.
> 
> Do I just paste it into the KEYS file on people.apache.org?  What
> about getting it signed?
> 
> --Ari
> 
> On Thu, Jul 2, 2009 at 9:09 AM, Owen O'Malley<oom@yahoo-inc.com> wrote:
>> 
>> On Jul 1, 2009, at 5:25 PM, Eric Yang wrote:
>> 
>>> Hi Ari,
>>> 
>>> I have made a public key for chukwa at
>>> people.apache.org:/www/www.apache.org/dist/hadoop/chukwa/KEYS.  I will
>>> take
>>> care of signing, if you could point me to the tarball.  Thanks
>> 
>> The Chukwa committers should generate gpg keys for themselves and add them
>> to chukwa/KEYS. There should *not* be a generic Chukwa key. The releases
>> should be signed by the committer that made the release.
>> 
>> -- Owen
>> 
> 
> 


Mime
View raw message