...

1. They need to be a Rya Commiter
   
   As a Rya Commiter, the Release Manager will have access to several really important tools used throughout the release process.   This includes write access to the official Apache Rya Git Repo, the Apache Jenkins Server, and the Apache Nexus Server.
   
   
2. Checkout and Build Rya
   
   The Release Manager should verify that they can checkout, build, and test Apache Rya on their machine.
   
   

   1. Checkout code from Git

      Code Block
      git clone https://git-wip-us.apache.org/repos/asf/incubator-rya.git incubator-rya-apache

   2. Build and Test Apache Rya

      Code Block
      mvn clean install

3. Setting up a PGP Key
   
   The Release manager needs a PGP Key and this key needs to be public.
   
   1. Getting software
   2. creating a key
   3. publishing a key
   4. adding your key to id.apache.org
   5. Adding your key to project key list (we currently don't have this)
4. Setting up Maven to push to apache repo
   1. Username/pass in maven settings
5. Testing settings
   1. Testing locally: 
      1. mvn clean install -Papache-release

   2. Testing by pushing to apache snapshot repo

      1. mvn clean deploy -Papache-release

6.  The first two items listed here need to be done (i.e. get some software to create a key, and create a key).  I'm not sure about the last three.
   
   1. Getting software

      1. Use gpg-agent, and be sure to increase the gpg-agent cache timeout (via .gnupg/gpg-agent.conf) to ensure that the agent doesn’t require re-authentication mid-build, as it will cause things to fail. For example, you can add default-cache-ttl 6000 to increase the timeout from the default of 10 minutes to over an hour. If you do not have a GPG key, reference the very thorough ASF release signing documentation.

   (

   1. 1. make sure you reset gpg-agent:

         echo RELOADAGENT | gpg-connect-agent

   2. Creating a key
   3. Publishing a key to a public server
   4. Adding your key to id.apache.org
   5. Adding your key to project key list (we currently don't have this)
7. Setting up Maven to push to apache repo
   1. Username/pass in maven settings
8. Testing settings
   1. Testing locally: 
      1. mvn clean install -Papache-release

   2. Testing by pushing to apache snapshot repo

      1. mvn clean deploy -Papache-release

Staging a release

note: I followed these instructions: http://www.apache.org/dev/publishing-maven-artifacts.html#prepare-poms

...