Releasing Ambari

# Generate RSA Keys
 mkdir ~/.ssh
 chmod 700 ~/.ssh
 ssh-keygen -t rsa -b 4096

# Note: This will create ~/.ssh/id_rsa and ~/.ssh/id_rsa.pub files will be generated
 
# Upload Public RSA Key
Login at http://id.apache.org
Add Public SSH Key to your profile from ~/.ssh/id_rsa.pub 
SSH Key (authorized_keys line):  
Submit changes
 
# Verify SSH to minotaur.apache.org works
ssh -i ~/.ssh/id_rsa {username}@minotaur.apache.org
 
# SFTP to home.apache.org
sftp {username}@home.apache.org
mkdir public_html
cd public_html
put test #This test file is a sample empty file present in current working directory from which you sftp. 
Verify URL http://home.apache.org/{username}/test

Subject: Preparing Ambari X.Y.Z branch

Hi developers and PMCs,

I am proposing cutting a new branch branch-X.Y for Ambari X.Y.Z on __________  as per the outlined tasks in the Ambari Feature + Roadmap page (https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=30755705).
After making the branch, we (i.e., development community) should only accept blocker or critical bug fixes into the branch and harden it until it meets a high enough quality bar. 
If you have a bug fix, it should first be committed to trunk, and after ensuring that it does not break any tests (including smoke tests), then it should be integrated to the Ambari branch-X.Y
If you have any doubts whether a fix should be committed into branch-X.Y, please email me for input at ____________
Stay tuned for updates on the release process.


Thanks

git checkout branch-X.Y

# Generate the following artifacts: 
# - Configuration markdown at docs/configuration/index.md
# - swagger.json and index.html at docs/api/generated/
cd ambari-server/
mvn clean compile exec:java@configuration-markdown test -Drat.skip -Dcheckstyle.skip -DskipTests -Dgenerate.swagger.resources
 
# Review and Commit the changes to branch-X.Y 
git commit

# Update the revision property to the release version
mvn versions:set-property -Dproperty=revision -DnewVersion=2.8.0.0.0

# Remove .versionsBackup files
git clean -f -x
 
# Review and commit the changes to branch-X.Y
git commit

gpg2 --list-keys jluniya@apache.org >> KEYS
gpg2 --armor --export jluniya@apache.org >> KEYS
 
# commit the changes to both trunk and new release branch
git commit
 
# push the updated KEYS file to https://dist.apache.org/repos/dist/release/ambari/.
# Only PMCs members can do this 'svn' step.
svn co https://dist.apache.org/repos/dist/release/ambari ambari_svn
cp {path_to_keys_file}/KEYS ambari_svn/KEYS
svn update KEYS
svn commit -m "Updating KEYS for Ambari"

# push the updated KEYS file to https://dist.apache.org/repos/dist/dev/ambari/.
svn co https://dist.apache.org/repos/dist/dev/ambari ambari_dev_svn
cp {path_to_keys_file}/KEYS ambari_dev_svn/KEYS
cd ambari_dev_svn
svn add KEYS 
svn commit -m "Updating KEYS for Ambari dev directory"

git checkout branch-X.Y

git tag -a release-X.Y.Z-rc0 -m 'Ambari X.Y.Z RC0'
git push origin release-X.Y.Z-rc0

 # create a clean copy of the source
 cd ambari-git-X.Y.Z
 git clean -f -x -d
 cd ..
 cp -R ambari-git-X.Y.Z apache-ambari-X.Y.Z-src
 
 # create ambari-web/public by running the build instructions per https://cwiki.apache.org/confluence/display/AMBARI/Ambari+Development
 # once ambari-web/public is created, copy it as ambari-web/public-static
 cp -R ambari-git-X.Y.Z/ambari-web/public apache-ambari-X.Y.Z-src/ambari-web/public-static
 
 # make sure apache rat tool runs successfully
 cp -R apache-ambari-X.Y.Z-src apache-ambari-X.Y.Z-ratcheck
 cd apache-ambari-X.Y.Z-ratcheck
 mvn clean apache-rat:check
 cd ..
 # if rat check fails, file JIRAs and fix them before proceeding.
 
 # tar it up, but exclude git artifacts
 tar --exclude=.git --exclude=.gitignore --exclude=.gitattributes -zcvf apache-ambari-X.Y.Z-src.tar.gz apache-ambari-X.Y.Z-src

gpg2  --armor --output apache-ambari-X.Y.Z-src.tar.gz.asc --detach-sig apache-ambari-X.Y.Z-src.tar.gz

sha512sum apache-ambari-X.Y.Z-src.tar.gz > apache-ambari-X.Y.Z-src.tar.gz.sha512

openssl sha512 apache-ambari-X.Y.Z-src.tar.gz > apache-ambari-X.Y.Z-src.tar.gz.sha512

# Check out the development version of the Ambari repository from Apache SVN
svn co https://dist.apache.org/repos/dist/dev/ambari ambari_dev_svn

# Create a new directory for the specific release candidate version
mkdir ambari_dev_svn/ambari-X.Y.Z-rc0

# Copy the source tarball into the newly created release candidate directory
cp apache-ambari-X.Y.Z-src.tar.gz ambari_dev_svn/ambari-X.Y.Z-rc0/

# Copy the corresponding GPG signature file into the release candidate directory
cp apache-ambari-X.Y.Z-src.tar.gz.asc ambari_dev_svn/ambari-X.Y.Z-rc0/

# Copy the SHA-512 checksum file into the release candidate directory
cp apache-ambari-X.Y.Z-src.tar.gz.sha512 ambari_dev_svn/ambari-X.Y.Z-rc0/

# Add all new files to SVN version control
svn add *

# Commit the changes to the SVN repository with a message indicating the release version
svn --username=${Apache username} commit -m "release X.Y.Z-rc0"

https://git-wip-us.apache.org/repos/asf/ambari/repo?p=ambari.git;a=log;h=refs/tags/release-x.y.z-rc0

svn co https://dist.apache.org/repos/dist/release/ambari ambari

# Note : Only PMCs members can do this 'svn' step.
cd ambari
svn mv https://dist.apache.org/repos/dist/dev/ambari/apache-ambari-X.Y.Z-rc0 https://dist.apache.org/repos/dist/release/ambari/ambari-X.Y.Z
svn add ambari-X.Y.Z
svn rm ambari-A.B.C  # Remove the older release from the mirror.  Only the latest version should appear in dist.
svn commit -m "Committing Release X.Y.Z"

git tag -a release-X.Y.Z -m 'Ambari X.Y.Z'
git push origin release-X.Y.Z

cd docs
mvn versions:set -DnewVersion=X.Y.Z

# Make necessary changes, typically to pom.xml, site.xml, index.apt, and whats-new.apt
mvn clean site