Page History

...

You need a passphrase to unlock the secret key for
user: "Rashmi Raghu (CODE SIGNING KEY) <rashmiraghu@apache.org>"
4096-bit RSA key, ID 28D2C789, created 2017-05-01 

$ ls -gGnl


-rw-r--r-- @ 1 20 7975215 Mar 30 15:42 apache-madlib-1.18.0-bin-Darwin.dmg

-rw-r--r-- 1 20 833 Mar 31 12:36 apache-madlib-1.18.0-bin-Darwin.dmg.asc

-rw-r--r-- 1 20 166 Mar 31 12:36 apache-madlib-1.18.0-bin-Darwin.dmg.sha512

-rw-rw-r-- 1 20 10275892 Mar 30 17:01 apache-madlib-1.18.0-bin-Linux-CentOS6.rpm

-rw-r--r-- 1 20 833 Mar 31 12:36 apache-madlib-1.18.0-bin-Linux-CentOS6.rpm.asc

-rw-r--r-- 1 20 173 Mar 31 12:36 apache-madlib-1.18.0-bin-Linux-CentOS6.rpm.sha512

-rw-rw-r-- 1 20 10387968 Mar 30 17:23 apache-madlib-1.18.0-bin-Linux-CentOS7.rpm

-rw-r--r-- 1 20 833 Mar 31 12:37 apache-madlib-1.18.0-bin-Linux-CentOS7.rpm.asc

-rw-r--r-- 1 20 173 Mar 31 12:37 apache-madlib-1.18.0-bin-Linux-CentOS7.rpm.sha512

-rw-rw-r-- 1 20 10737982 Mar 30 18:23 apache-madlib-1.18.0-bin-Linux-Ubuntu18.deb

-rw-r--r-- 1 20 833 Mar 31 12:37 apache-madlib-1.18.0-bin-Linux-Ubuntu18.deb.asc

-rw-r--r-- 1 20 174 Mar 31 12:37 apache-madlib-1.18.0-bin-Linux-Ubuntu18.deb.sha512

-rw-r--r-- 1 20 3156110 Mar 31 11:52 apache-madlib-1.18.0-src.tar.gz

...

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
      If the -u option doesn't work, then you can also try updating the global git config with your key (It might also be possible to update just the local git config instead of the global config but we haven't tried doing that)
      git config --global user.signingkey <KEY>
      git tag --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 change, 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.

...