This document describe describes the process to release apache Apache Hadoop Ozone. The process is not yet scripted, and the documentation is a work in progress
Pre-Requisite
Release The release manager should have a gpg key setup to sign the artifacts. For more details refer to below link.
https://www.apache.org/dev/new-committers-guide.html#set-up-security-and-pgp-keys
Publish your key
The key supposed to be published together with the release. Please append it to the end of KEYS files:
https://dist.apache.org/repos/dist/release/ozone/KEYS
| Code Block |
|---|
| language | bash |
|---|
| theme | RDark |
|---|
| title | Export Vars |
|---|
|
svn co https://dist.apache.org/repos/dist/release/ozone
cd ozone
export CODESIGNINGKEY=your_gpg_key_id
gpg --list-sigs $CODESIGNINGKEY >> KEYS
gpg --armor --export $CODESIGNINGKEY >> KEYS
svn commit -m "ozone: adding key of XXXX to the KEYS" |
In case you are only a committer and not a PMC member, you can add your key to the dev KEYS file and a PMC can move it to the final destination
| Code Block |
|---|
| language | bash |
|---|
| theme | RDark |
|---|
| title | Export Vars |
|---|
|
#use latest KEYS as the base
svn rm https://dist.apache.org/repos/dist/dev/ozone/KEYS
svn cp https://dist.apache.org/repos/dist/release/ozone/KEYS https://dist.apache.org/repos/dist/dev/ozone/KEYS
svn co https://dist.apache.org/repos/dist/dev/ozone
cd ozone
export CODESIGNINGKEY=your_gpg_key_id
gpg --list-sigs $CODESIGNINGKEY >> KEYS
gpg --armor --export $CODESIGNINGKEY >> KEYS
svn commit -m "ozone: adding key of XXXX to the KEYS" |
Please include the URL of the used KEYS file in your VOTE mail!
Pre-Vote
Set up environment variables
...
| Code Block |
|---|
|
for i in $(ls -1 *.tar.gz); do gpg -u ${CODESIGNINGKEY} --armor --output "${i}.asc" --detach-sig "${i}"; done
for i in $(ls -1 *.tar.gz); do sha512sum ${i} > ${i}.sha512; done
for i in $(ls -1 *.tar.gz); do gpg --print-mds ${i} > ${i}.mds; done |
Upload the artifacts
...
dev staging area
- Upload everything from the $RELEASE_DIR to your apache home with sftpthe dev staging area
| Code Block |
|---|
| language | bash |
|---|
| theme | RDark |
|---|
| title | FTP to the apache server |
|---|
|
sftp homesvn mkdir https://dist.apache.org |
- Create a directory called "public_html" if it does not exist.
| Code Block |
|---|
| language | bash |
|---|
| theme | RDark |
|---|
| title | Create public_html |
|---|
|
mkdir public_html |
- Create the Release Directory
| Code Block |
|---|
| language | bash |
|---|
| theme | RDark |
|---|
| title | Create the Release Directory under public_html |
|---|
|
mkdir public_html/ozone-1.1.0-rc0/ |
- Change directory into the new release directory
| Code Block |
|---|
| language | bash |
|---|
| theme | RDark |
|---|
| title | Move into the release directory |
|---|
|
cd public_html/ozone-0.4.0-alpha-rc0 |
- Upload the release artifacts to this release directory
| Code Block |
|---|
| language | bash |
|---|
| theme | RDark |
|---|
| title | Upload Release Artifacts |
|---|
|
mput * |
/repos/dist/dev/ozone/1.2.0-rc0
svn co https://dist.apache.org/repos/dist/dev/ozone/1.1.0-rc2
cd 1.1.0-rc2 |
- Copy all the release files to the new directory and commit them
- Check the results using your browser by connecting to to https://homedist.apache.org/~<apacheName>repos/dist/dev/ozone-0.4.0-alpha-rc0/
Upload the artifacts to the apache nexus
...
Send the voting mail to below mailing list
- Hadoop Common dev@ozone <dev@ozone.apache.org>
Vote
...