svn commit: r1438181 - /airavata/site/trunk/content/development/release-management.mdtext

[sm...@apache.org]

Author: smarru
Date: Thu Jan 24 20:49:20 2013
New Revision: 1438181

URL: http://svn.apache.org/viewvc?rev=1438181&view=rev
Log:
adding key signing instructions

Modified:
    airavata/site/trunk/content/development/release-management.mdtext

Modified: airavata/site/trunk/content/development/release-management.mdtext
URL: http://svn.apache.org/viewvc/airavata/site/trunk/content/development/release-management.mdtext?rev=1438181&r1=1438180&r2=1438181&view=diff
==============================================================================
--- airavata/site/trunk/content/development/release-management.mdtext (original)
+++ airavata/site/trunk/content/development/release-management.mdtext Thu Jan 24 20:49:20 2013
@@ -41,6 +41,14 @@ The steps can be summerized as: 
 * Have your key signed by atleast three apache commiters, [key signing][key-sign] and [Henk Penning][henk-trust] websites provide instructions.
 * Add the signed public key to the KEYS file on [Airavata Dist SVN][airavata-dist-svn].
 
+For reference, the steps to sign a key:
+
+* The person whom you know in person provides you his key, usually this happens at key signing party where you can verify each others ID's. 
+* Fetch the key `gpg --keyserver <keyserver> --recv-keys <Key_ID>` an example key server is pgp.mit.edu
+* Sign the key `gpg --sign-key <Key_ID>`
+* Upload the key back to the server `gpg --keyserver <keyserver> --send-key <Key_ID>`
+
+
 <a name="maven-nexus-setup"></a>
 #### Maven Configuration & Nexus Setup