Table of Contents

Preliminaries

Permission requirements

The following permissions are required to perform release manager duties.

• Apache dist server (https://dist.apache.org/repos/dist) subversion privileges (PMC Member)
• Applying git release tags (Project committer)

Apache Release Documentation

• Apache Release Guide
• Apache Release Policy

...

1. Update the wiki with these release notes for the new release
2. Update the release notes file in the source code: https://github.com/rashmi815/incubator-madlib/blob/master/RELEASE_NOTES (create PR and merge)

Prepare Tarballs

1. Branch your release:

   Created signed annotated git tag on release branch

   
   

   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 tag -u <GPG KEY ID> --sign <your release name>-rc# -m "Apache MADlib <your release name> RC#" <SHA of HEAD of branch>
   
   Example:

    $ git tag -u 57325522 --sign rc/1.12-rc1 -m "Apache MADlib 1.12 RC1" 46795de0254d2cb7755ee9336be5fef2a187e8c9

    

2. Make a tarball and gzip:
   

   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:

   $ git archive -o ../apache-madlib-1.1112-src.tar --prefix=apache-madlib-1.1112-src/ rc/1.1112-rc1
   $ gzip ../apache-madlib-1.1112-src.tar

NOTE: Depending on release requirements, an alternate approach is to create a release branch to which the tag will be applied. 

• Branch your release:

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

push to origin:

git push origin <your release name>

Create convenience binaries (rpm and dmg files)

...