Currently, this is just a collection area for my rough notes and what-not.  It will soon be a much cleaner guide.

Speaking of guides, here Here are a bunch of good onesguides:

http://accumulo.apache.org/releasing.html
http://accumulo.apache.org/verifying_releases.html

http://yetus.apache.org/contribute/releases/

How to Release Sqoop2 

How to Improve this Page

The purpose of this page is to document the mechanics of a release.  I took this phrase from the NiFi Release Guide (http://nifi.apache.org/release-guide.html) because I really like their outline and guide.  Eventually, we should incorporate other aspects into this guide including:

...

The flow of a release (an outline)

(Feel free to toss in any additional sections here)

The mechanics of the release  

Release Manager

...

First-Time Preparation

Before a Release Manager begins cutting a release of Apache Rya, there are a handful of Dependencies and one-time Prerequisites they need to satisfy:

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-usgitbox.apache.org/repos/asf/incubator-rya.git incubator-rya-apacherya cd rya

      
      

   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.  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. Get GPG.  (PGP should work as well, but this guide uses GPG).  It is probably already available in your linux distro.

      2. Get

      3. 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. make sure you reset gpg-agent:

      4. Here is a working example of ~/.gnupg/gpg-agent.conf
         

         default-cache-ttl 28800
# 8 hours
pinentry-program /usr/bin/pinentry-curses
allow-loopback-pinentry

      5. 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
4. Setting up Maven to push to apache repo
   
   1. Username/pass in maven settings
5. Add Key to KEYS file

   1. https://dist.apache.org/repos/dist/release/incubator/rya/KEYS

6. 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 (super short edition):

git checkout -b 3.2.10-RC2 master

mvn clean release:prepare -Darguments="-DskipTests"

1. 1. 1. 
         

      2. Using Fedora, might need to use gpg2.  These two must match:

         1. gpg --version

         2. gpg-agent --version
            If they don't, check for version 2:
         1. gpg2 --version
         2. I was able to copy/link the commands in /usr/bin/:  mv gpg  gpg1 and ln -s gpg2  gpg
            
            
   2. Creating a key If you do not have a GPG key, reference the very thorough ASF release signing documentation available at https://www.apache.org/dev/release-signing.html.
   3. Publishing a key to a public server
   4. Adding your key to id.apache.org
2. Setting up Maven to push to apache repo
   
   1. Username/pass in maven settings
3. Add Key to KEYS file

   1. See it here:

      https://dist.apache.org/repos/dist/release/rya/KEYS

      
      

   2. Do this with your name where it says "David":

      svn checkout https://dist.apache.org/repos/dist/release/rya
      (gpg --list-sigs "David"    && gpg --armor --export "David") >> rya/KEYS 
      cd rya
      svn commit -m "Adding David to KEYS"

      
      

4. 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

   3. Testing private key use and gpg-agent prompting.  This is a way to preload the key before the release build below.  Do this with your name (Unique initial characters of the full name are accepted) where it says "David":
      1. eval $(gpg-agent --daemon) ### Start the gpg-agent if not already.
         

      2. echo "hello" >> text.txt

      3. gpg -e -u "Aaron" -r "David" text.txt  ### These names are actually in the Rya keys file.


      4. gpg -d text.txt.gpg   ### this will prompt for David's key decrypt password and cache it.

         
         

Staging a Release

git checkout -b 4.0.1-RC2 master

5. Build Rya, prepare and perform release.  This takes about 50 minutes.  At this point you must have the gpg-agent running and probably have the password cached.  It has failed without asking.  See the preparation section for details on testing private key use (6c).  It will ask several things, release names quoted below, and Apache committer username and password a few times, currently 3 times.

mvn clean release:prepare -Pgeoindexing -Pbenchmark -Pgiraph -Darguments="-DskipTests"

What is the release version for "Apache Rya Project"? (org.apache.rya:rya-project) 4.0.1: : 
What is SCM release tag or label for "Apache Rya Project"? (org.apache.rya:rya-project) v4.0.1: : rya-4.0.1-rc1
What is the new development version for "Apache Rya Project"? (org.apache.rya:rya-project) 4.1.0-SNAPSHOT: : 

<?xml version="1.0" encoding="UTF-8"?>
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">
   <servers>
     <server>
       <id>apache.releases.https</id>
       <username>PUT_USERID_HERE</username>
       <password>PUTPASSWORDHERE</password>
     </server>
   </servers>
   <pluginGroups></pluginGroups>
   <proxies></proxies>
   <mirrors></mirrors>
   <profiles></profiles>
</settings>

mvn release:perform -Darguments="-DskipTests"

cd ..
svn checkout https://dist.apache.org/repos/dist/dev/rya
cd rya
mkdir rya-4.0.1-rc3
cd rya-4.0.1-rc3
 
cp ../../rya/target/checkout/target/rya-project-4.0.1-source-release.zip* .
openssl sha512 -r rya-project-4.0.1-source-release.zip > rya-project-4.0.1-source-release.zip.sha512
 
cd ..
 
svn add rya-4.0.1-rc3
svn commit -m "Adding rya-4.0.1-rc3"

What is the release version for "Apache Rya Project"? (org.apache.rya:rya-project) 3.2.10-incubating: : 
What is SCM release tag or label for "Apache Rya Project"? (org.apache.rya:rya-project) v3.2.10-incubating: : rya-incubating-3.2.10-rc2
What is the new development version for "Apache Rya Project"? (org.apache.rya:rya-project) 3.2.11-incubating-SNAPSHOT: : 

mvn release:perform -Darguments="-DskipTests"

svn checkout https://dist.apache.org/repos/dist/dev/incubator/rya
(double check that last command)
mkdir rya-incubating-3.2.10-rc3
cd rya-incubating-3.2.10-rc3
 
cp ../../incubator-rya-apache/target/checkout/target/rya-project-3.2.10-incubating-source-release.zip.* .
md5 -r rya-project-3.2.10-incubating-source-release.zip > rya-project-3.2.10-incubating-source-release.zip.md5
shasum -a 1 rya-project-3.2.10-incubating-source-release.zip > rya-project-3.2.10-incubating-source-release.zip.sha1
 
cd ..
 
svn add rya-incubating-3.2.10-rc3
svn commit -m "Adding rya-incubating-3.2.10-rc3"

rm DEPENDENCIES
mkdir /tmp/new_m2
cp $M2_HOME/conf/settings.xml /tmp/new_m2/settings.xml
mvn --settings /tmp/new_m2settings.xml -Dmaven.repo.local=/tmp/new_m2 clean package

find . -type f  | grep -v '\/test\/\|\/site\/\|\.java\|\.xml\|\.xsl\|\.groovy\|\.properties\|\.sh\|\.bat\|\.md\|\.txt'

find . -type f | xargs du -sh | grep [GM]\\s

rm DEPENDENCIES
mkdir /tmp/new_m2
cp $M2_HOME/conf/settings.xml /tmp/new_m2/settings.xml
mvn --settings /tmp/new_m2settings.xml -Dmaven.repo.local=/tmp/new_m2 clean package

find . -type f | grep -v '\/target\/\|\/test\/\|\/site\/\|\.java\|\.xml\|\.xsl\|\.groovy\|\.properties\|\.sh\|\.bat\|\.md\|\.txt'

find . -type f | xargs du -sh | grep [GM]\\s

To: dev@rya.apache.org
Subject: [VOTE] Release Rya version 4.0.1 RC2

I am pleased to be calling this vote for the source release of Apache Rya, version 4.0.1.
 
The source zip, including signatures, digests, etc. can be found at:
https://dist.apache.org/repos/dist/dev/rya/rya-4.0.1-rc2/

Ancillary artifacts such as poms, jars, wars, ect. can be found here:
https://repository.apache.org/content/repositories/orgapacherya-1002/org/apache/rya/rya-project/4.0.1/

The Git tag is rya-4.0.1-rc2
The Git commit ID is 9f0d63e6089df172eb3f41957d2956ec0035953a
https://gitbox.apache.org/repos/asf/rya.git;a=commit;h=9f0d63e6089df172eb3f41957d2956ec0035953a
 
Checksums of rya-project-4.0.1-source-release.zip:
SHA512: b6ae761aa42f80e1cb84bb645184e29e4436eaaaf66aa7249aa65b6adb38f3dfdd9a6f8b536eb0e2de88ac75cc2a0c8d97d85b4dd0ffef7f9407e05642110b3f
 
Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/mihalik.asc

KEYS file available here:
https://dist.apache.org/repos/dist/release/rya/KEYS
 
Issues that were closed/resolved for this release are here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12334209&styleName=Html&projectId=12319020
 
Issues resolved between RC1 and RC2 are here:
https://issues.apache.org/jira/browse/RYA-184

The vote will be open for at least 72 hours and close after <Date Time and Timezone>.
Please download the release candidate and evaluate the necessary items including checking hashes, signatures, build from source, and test.  Then please vote:
 
[ ] +1 Release this package as rya-project-4.0.1
[ ] +0 no opinion
[ ] -1 Do not release this package because because...

To: dev@rya.apache.org
Subject: [RESULT] [VOTE] Release Rya version 4.0.1 RC1

Hello,

The vote to release Rya version 4.0.1 RC1 has failed.

+1 (binding):

(Members of PMC)

+1 (non binding):

(Everyone else)

(List of series of tasks that have been created or already exist that block the release)
The following Jira tasks have been created to capture the issues blocking a successful release:
 
RYA-XXX <Issue Title> [1]
RYA-XXX <Issue Title> [2]
RYA-XXX <Issue Title> [3]


(Create an issue that links to all of these issues)
The following Jira task has been created to capture all of the issues that will be resolved in the next RC:

RYA-XXX Perform 4.0.1-RC<N+1> Release [4]
 
These tasks should address the concerns raised during the voting process.

To: dev@rya.apache.org
Subject: [RESULT] [VOTE] Release Rya version 4.0.1 RC1

Hello,

The vote to release Rya version 4.0.1 RC1 has passed.

+1 (binding):

(Members of PMC)



+1 (

To: dev@rya.incubator.apache.org
Subject: [RESULT] [VOTE] Release Rya (Incubating) version 3.2.10 RC1

Hello,

The vote to release Rya (Incubating) version 3.2.10 RC1 has failed.

+1 (binding):

(Members of PPMC)

+1 (non binding):

(Everyone else)

(List of series of tasks that have been created or already exist that block the release)
The following Jira tasks have been created to capture the issues blocking a successful release:
 
RYA-XXX <Issue Title> [1]
RYA-XXX <Issue Title> [2]
RYA-XXX <Issue Title> [3]


(Create an issue that links to all of these issues)
The following Jira task has been created to capture all of the issues that will be resolved in the next RC:

RYA-XXX Perform 3.2.10-RC<N+1> Release [4]
 
These tasks should address the concerns raised during the voting process.

To: dev@rya.incubator.apache.org
Subject: [RESULT] [VOTE] Release Apache Rya (Incubating) version 3.2.10 RC3


This vote passes with +<N> Binding and +<N> Non-binding votes. 
 
+1 (binding):

(Members of PPMC)


+1 (non binding):

(Everyone else)
 
I'll be sending a vote email to the IPMC soon
 

To: dev@rya.incubator.apache.org, general@incubator.apache.org
Subject: [VOTE] Release Apache Rya (Incubating) version 3.2.10 RC3

The Apache Rya community has voted and approved the proposed release of Apache Rya 3.2.10 (Incubating) RC3.


We now kindly request the Incubator PMC members review and vote on this incubator release.

Rya (pronounced "ree-uh" /rēə/) is a cloud-based RDF triple store that supports SPARQL queries. Rya is a scalable RDF data management system built on top of Apache Accumulo®. Rya uses novel storage methods, indexing schemes, and query processing techniques that scale to billions of triples across multiple nodes. Rya provides fast and easy access to the data through SPARQL, a conventional query mechanism for RDF data. More information can be found at http://rya.incubator.apache.org/

[VOTE] Thread:
https://lists.apache.org/thread.html/01d692717b2ee088253fa96c42759309a2a4d2aaf9867905bc473fa7@%3Cdev.rya.apache.org%3E

[VOTE RESULT] Thread:
https://lists.apache.org/thread.html/e58e7456987d74f11a0698fd5d4dde436bd83016baa269c149f03511@%3Cdev.rya.apache.org%3E
 
<cut and paste from vote email on dev list.

To: dev@rya.incubator.apache.org, general@incubator.apache.org
Subject: [RESULT] [VOTE] Release Rya (Incubating) version 3.2.10 RC1

Hello,

The vote to release Rya (Incubating) version 3.2.10 RC1 has passed.

+1 (binding):

(Members of PPMC)
(Members of IPMC)



+1 (non binding):

(Everyone else)

IThank willyou promoteall the for voting!
I will promote the artifacts to the central reporepository.
 

To: announce@apache.org, dev@rya.incubator.apache.org, general@incubator.apache.org
Subject: [ANNOUNCE] Apache Rya 34.20.10-incubating1 released
 
The Apache Rya (Incubating) team is happy to announce the release of Apache Rya 34.20.10-incubating1:

https://rya.incubator.apache.org/release/rya-34.20.10-incubating1/

Rya (pronounced "ree-uh" /rēə/) is a cloud-based RDF triple store that supports SPARQL queries. Rya is a scalable RDF data management system built on top of Apache Accumulo®. Rya uses novel storage methods, indexing schemes, and query processing techniques that scale to billions of triples across multiple nodes. Rya provides fast and easy access to the data through SPARQL, a conventional query mechanism for RDF data.

[Include highlights of changes in this release]


Thanks,
The Apache Rya team

=====

*Disclaimer*

Apache Rya (incubating) is an effort undergoing Incubation at The Apache Software Foundation (ASF), sponsored by the Incubator. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.

git tag -d v3.2.10-RC1
git push origin :refs/tags/v3.2.10-RC1
 
git branch -D 3.2.10-RC1
git push origin --delete 3.2.10-RC1

>> mvn license:aggregate-add-third-party

egrep -iv "BSD|ASF|MIT|CDDL|EPL|Apache|Eclipse|Public Domain" target/generated-sources/license/THIRD-PARTY.txt

git tag -d v4.0.1-RC1
git push origin :refs/tags/v4.0.1-RC1
 
git branch -D 4.0.1-RC1
git push origin --delete 4.0.1-RC1

>> mvn license:aggregate-add-third-party

egrep -iv "BSD|ASF|MIT|CDDL|EPL|Apache|Eclipse|Public Domain" target/generated-sources/license/THIRD-PARTY.txt

References:

http://www.apache.org/dev/publishing-maven-artifacts.html