...
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/
Remove old releases from the dev dist sites
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>
- Delete the folders from local working copy using
svn delete <folder to delete>
.
E.g.svn delete 1.12.RC1/
- Commit the deletions:
svn commit -m 'Removing 1.12 RC releases' --username=<your apache user id>
- 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:
- Upload latest release documentation (including docs/latest symlink)
- Update Download page
- Upload latest design.pdf
- Update MADlib home page with release news
- Apply release tag referencing git hash representing final release candidate:
git tag -u 57325522 --sign rel/v1.12 -m "Apache MADlib 1.12" 46795de0254d2cb7755ee9336be5fef2a187e8c9
git push upstream <your release tag>
- Announce the release on announce@apache.org, user@madlib.apache.org and dev@madlib.apache.org mailing lists. See example email of past announcement.
...