...

• Add your code signing key to your Apache ID here
• Publish it to a public key server such as the MIT key server.
• Add it to the HAWQ KEYS files in the dev and release subversion repositories:
  • dev: https://dist.apache.org/repos/dist/dev/incubator/hawqmadlib/KEYS
  • release: https://dist.apache.org/repos/dist/devrelease/incubator/hawqmadlib/KEYS

Ensure JIRA Issues are Appropriately Tagged for the Release 

...

Create the Release Candidate

Prepare Tarballs

Send email to dev@madlib.incubator.apache.org for instructions on how to do this.

Some basic steps are listed below.

Branch your release:

git checkout -b <your release name> <commit sha1>

push to origin:
git push origin <your release name>

...

Apply signed tag on release branch

Example:

 git tag -u <GPG KEY ID> --sign <your release name>-rc# -m "Apache MADlib <your release name> RC#" <SHA of HEAD of branch>

Prepare rpm and dmg binaries

Send email to dev@madlib.incubator.apache.org for instructions on how to do this.

Sign the Release Candidate

Check that md5, shasum, and gpg (or gpg2) are installed on your machine:

$ which md5
/sbin/md5

$ which shasum
/usr/bin/shasum

$ which gpg
/usr/local/bin/gpg

Install using Hombrew (on Mac OS) if needed e.g.:

...

git archive -o ../apache-madlib-<your release name>-src.tar --prefix=apache-madlib-<your release name>-src/ <your tag/branch name>
gzip ../apache-madlib-<your release name>-src.tar

Example:

...

Prepare rpm and dmg binaries

Send email to dev@madlib.incubator.apache.org for instructions on how to do this.

...

Prepare MD5, SHA256 and ASC files from the source tarball and binaries:

md5 <your release tarball or binary> > <your release tarball or binary>.md5
shasum -a 512 <your release tarball or binary> > <your release tarball or binary>.sha512 
gpg --detach-sign -a <your release tarball or binary>

...