You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 22 Next »

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 are a bunch of good ones:

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

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

How to Release Sqoop2

 

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:

Background Material

What to validate and how to Validate a release

The flow of a release (an outline)

 

(Feel free to toss in any additional sections here)


The mechanics of the release  

Release Manager Dependencies

Before a Release Manager begins cutting a release of Apache Rya, there are a handful of Dependencies and 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 

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

    2. Build and Test Apache Rya

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

        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)
  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

Staging a release

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

  1. Checkout Rya

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

  2. Create a Release Branch

    1. git checkout -b 3.2.10-RC1 master

  3. Build a push a signed snapshot

    1. mvn clean deploy -Papache-release

  4. Do some manual checks (note I think that the mvn release plugin does all of this)

    1. Make sure there are no dependencies on snapshots in the POMs to be released

    2. Check that your POMs will not lose content when they are rewritten during the release process

      1. mvn release:prepare -Papache-release -DdryRun=true -Darguments="-DskipTests"

      2. Diff the original file pom.xml with the one called pom.xml.tag to see if the license or any other info has been removed

      3. What is the release version for "Apache Rya Project"? (org.apache.rya:rya-project) 3.2.10: : 

        What is SCM release tag or label for "Apache Rya Project"? (org.apache.rya:rya-project) rya-project-3.2.10: : 3.2.10

        What is the new development version for "Apache Rya Project"? (org.apache.rya:rya-project) 3.2.11-SNAPSHOT: : 


  5. Prepare release

    1. mvn release:clean

    2. mvn release:prepare

  6. Stage release for a vote
    1. mvn release:perform

       

 

super short edition:

1.Checkout out code
2. Create release candidate branch

 

git checkout -b 3.2.10-RC1 master
git push -u origin 3.2.10-RC1

 

3. Build Rya, prepare and perform release

 

mvn clean package -Papache-release
mvn release:prepare

 

 

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

 

 

mvn release:perform

 

Once the release has been performed, the artifacts should be in a staging repository:
From "Publishing Maven Artifacts" page:
Now you must close the staging repository to indicate to Nexus that the build is done and to make the artifacts available. Follow the steps in Closing the Staged Repositoryto close your new repository, this will allow your community to VOTE on the staged atrifacts.

Download the src artifact and performs some simple tests:

  • Download the sources and verify they compile cleanly.
  • Validate the hashes match.
  • Validate that the sources contain no unexpected binaries.
  • Validate the signature for the build and hashes.
  • Validate the LICENSE/NOTICE/Headers.

 Other release checklists:

http://wiki.apache.org/incubator/ReleaseChecklist

http://incubator.apache.org/guides/releasemanagement.html#check-list


Commands to build Rya with a Fresh Maven Repo and Settings.xml
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

 

 

Command to Check for Binary Files
find . -type f  | grep -v '\/test\/\|\/site\/\|\.java\|\.xml\|\.xsl\|\.groovy\|\.properties\|\.sh\|\.bat\|\.md\|\.txt'

 

 

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

 

Send out a Vote email (make sure to include some sort of "RC-X" identifier in the vote subject so that we can differentiate them in the archives)

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

I am pleased to be calling this vote for the source release of Apache Rya (Incubating), version 3.2.10.

The source zip, including signatures, digests, etc. can be found at:
https://repository.apache.org/content/repositories/orgapacherya-1001/org/apache/rya/rya-project/3.2.10/
 
The Git tag is v3.2.10
The Git commit ID is 16196b4c658062545964602835cb5fbd2870e578
https://git-wip-us.apache.org/repos/asf?p=incubator-rya.git;a=commit;h=16196b4c658062545964602835cb5fbd2870e578
 
Checksums of rya-project-3.2.10-source-release.zip:
SHA1: dee4a5e4f8e74c4de614d02c7b17a5e0db132649
MD5: df4a47ae1232725bc95450f5e49de95c

Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/mihalik.asc

Issue that were closed/resolved for this release are here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12334209&styleName=Html&projectId=12319020

The vote will be open for 72 hours. 
Please download the release candidate and evaluate the necessary items including checking hashes, signatures, build from source, and test.  The please vote:

[ ] +1 Release this package as rya-project-3.2.10
[ ] +0 no opinion
[ ] -1 Do not release this package because because...

 

 

If there is something wrong with the staging repo:
delete the tag:

 

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
 

Rya uses Mini Accumulo Cluster for a number of it's tests and I've run into a number of gotchas:
  1. On windows, I've found that I need to update my hosts file to add my ip and my machine name (something like 10.aaa.bbb.ccc mymachinename)
  2. Close all VPNs
  3. Do not use strange DNS machines.  just use the default ones your network/isp provides
  4. McAfee Virus Scan may slow things down and throw off the test


References:

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

 



  • No labels