...

Create the Release Candidate

Prepare Tarballs

...

1. Branch your release:

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

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

   


2. Apply signed tag on release branch

   Example:

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

3. Make a tarball and gzip:
   

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

   Example:

   $ git archive -o ../apache-madlib-1.11-incubating-src.tar --prefix=apache-madlib-1.11-incubating-src/ 1.11-incubating
   $ gzip ../apache-madlib-1.11-incubating-src.tar

    

Prepare rpm and dmg binaries

...

Execute the following commands in the build directory:

$ cmake <path to source code directory>

$ make 

$ make package

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

Sign the Release Candidate

...

$ gpg --verify apache-madlib-1.11-incubating-bin-Linux.rpm.asc
gpg: assuming signed data in `apache-madlib-1.11-incubating-bin-Linux.rpm'
gpg: Signature made Mon May 1 14:42:16 2017 PDT using RSA key ID 28D2C789
gpg: Good signature from "Rashmi Raghu (CODE SIGNING KEY) <rashmiraghu@apache.org>"
$ gsha512sum --check apache-madlib-1.11-incubating-bin-Linux.rpm.sha512
apache-madlib-1.11-incubating-bin-Linux.rpm: OK
$ gmd5sum --check apache-madlib-1.11-incubating-bin-Linux.rpm.md5
apache-madlib-1.11-incubating-bin-Linux.rpm: OK

• Build is successful (Refer to Build and Install for build instructions)

Check Jenkins build here to make sure it does not show any errors: https://builds.apache.org/job/madlib-master-build/ 

• DISCLAIMER is correct, filenames include “incubating”

...

• All source files have license headers where appropriate, RAT checks passAdditional check:pom.xml (For artifactId "hawq", verify version is consistent with the version specified in getversion file in the root directory).

$ mvn apache-rat:check 

• The provenance of all source files is clear (ASF or software grants)

...

Commit artifacts to Apache dist site:

...

Uploading to this site is via SVN. Send email to dev@madlib.incubator.apache.org for instructions on how to do this. Subversion.

1. Retrieve the subversion dev incubator madlib repo
   Example: svn checkout https://dist.apache.org/repos/dist/dev/incubator/madlib/ --username=<your apache user>

2. Create a local folder for the release (e.g. 1.11-incubating.RC1) in svn. We use apache's distribution repo: https://dist.apache.org/repos/dist/dev/incubator/madlib/
3. Move the files into the release folder on local disk
4. svn add <release folder>
5. Commit artifacts:
   Example: svn commit -m 'adding 1.11-incubating RC1 candidate release artifacts' --username=<your apache user id>

...

Vote on the Release

General information regarding the Apache voting process can be found here: http://www.apache.org/foundation/voting.html. 

...