THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Release process
Preparing for release
Email dev@ambari.apache.org mailing list expressing your interest in volunteering to be the release manager for Apache Ambari X.Y.Z release:
Code Block |
---|
Subject: Release Manager for Ambari X.Y.Z Hi all, I would like to volunteer to be the release manager for Ambari X.Y.Z Thanks |
Wait for three +1s as confirmation.
Setup for first time release managers
If you are being a release manager for the first time, you will need to do the following steps so that you are not blocked during the actual release steps
Configure SSH to people.apache.org
SSH to people.apache.org supports only Key-Based SSH Logins
Code Block |
---|
# 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
# SSH to people.apache.org
ssh {username}@people.apache.org
mkdir public_html
cd public_html
touch test
Verify URL http://people.apache.org/{username}/test |
Generate OpenGPG Key
Code Block |
---|
gpg2 --gen-key
gpg2 --keyserver pgp.mit.edu --send-key CD23CAA
gpg2 --armor --export {username}@apache.org > {username}.asc
scp {username}.asc {username}@people.apache.org:public_html/~{username}.asc
Verify URL http://people.apache.org/~{username}/{username}.asc
Query PGP KeyServer http://pgp.mit.edu:11371/pks/lookup?search=0xCD23CAAE&op=vindex
Login at http://id.apache.org
Add OpenPGP Fingerprint to your profile
OpenPGP Public Key Primary Fingerprint: CD23CAA
Submit changes
Verify that the public PGP key is exported to http://people.apache.org/keys/committer/{username}.asc |
Email dev@ambari.apache.org mailing list notifying that you will be creating the release branch soon
Code Block |
---|
Subject: Preparing Ambari X.Y.Z branch Hi developers and PMCs, I am proposing cutting the branch 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 X.Y.Z branch. If you have any doubts whether a fix should be committed into the X.Y.Z branch, please email me for input at ____________ Stay tuned for updates on the release process. Thanks |
...