...

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

2. Create a local folder for the release (e.g. 1.11.RC1) in svn. We use apache's distribution repo: https://dist.apache.org/repos/dist/dev/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 RC1 candidate release artifacts' --username=<your apache user id>

Create a release candidate for MADlib user docs

The voting email needs to point to the release candidate user docs which are located at https://github.com/apache/madlib-site/tree/asf-site

1. Create a folder called rc in madlib-site/docs

2. Run make doc on the release tagged madlib source code

3. cp -r /path/to/madlib/build/doc/user/html/* /path/to/madlib-site/docs/rc/

4. Commit the changes to the asf-site branch of madlib-site repo.
5. While sending out the voting email, include http://madlib.apache.org/docs/rc/index.html as the documentation URL for the release candidate.

...

Vote on the Release

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

...

Please see the Apache voting process site for information on how many +1 votes are needed, what to do in case of -1 votes and for any clarifications to the voting process. 

Example email to the community calling for the vote can be found in Apache mail archives site here.

Once the community vote has been completed, the release manager must send out an email to the user and dev mailing lists with the results of the vote.  If other scenarios arise in the voting process, please refer to experienced community members or other similar projects for guidance on next steps.

...

1. Move the source, binaries and corresponding signature files from staging (dev) folder to the release dist site: https://dist.apache.org/repos/dist/release/madlib/ . Use the svn mv command. Example below:
   svn mv https://dist.apache.org/repos/dist/dev/madlib/1.12.RC1/ https://dist.apache.org/repos/dist/release/madlib/1.12/
   
   

2. Remove old releases from the dev dist sites

   1. Retrieve the subversion release madlib repo if you have not done so already
      Example: svn checkout https://dist.apache.org/repos/dist/dev/madlib/ --username=<your apache user id>

   2. Delete the folders from local working copy using svn delete <folder to delete>. 
      E.g. svn delete 1.12.RC1/
   3. Commit the deletions: svn commit -m 'Removing 1.12 RC releases' --username=<your apache user id>
3. Update the user docs link to point to the correct version of the docs and also update any version numbers / links in the page content: http://madlib.apache.org/docs/latest/. Update the MADlib website ... review previous release commits for details:
   1. Upload latest release documentation (including docs/latest symlink)
   2. Update Download page
   3. Upload latest design.pdf
   4. Update MADlib home page with release news
4. Apply release tag referencing git hash representing final release candidate:

   1. git tag -u 57325522 --sign rel/v1.12 -m "Apache MADlib 1.12" 46795de0254d2cb7755ee9336be5fef2a187e8c9

   2. git push upstream <your release tag>

5. In the asf-site branch of madlib-site repo,
   
   1. git mv the content of docs/rc folder into the latest release folder.
   2. Update the latest symlink to point to the latest release folder.
6. After doing the above chagechange, wait for at least 24 hours and then announce the release on announce@apache.org, user@madlib.apache.org and dev@madlib.apache.org mailing lists. See example email of past announcement.

...