Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Once the release candidate has successfully passed through the voting processes, it is ready to be GA.

  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/incubator/madlib/ .


    See section above on committing artifacts to the dev dist site for any steps that should have been completed prior to the steps below.Retrieve the subversion release incubator madlib repo
    Example: svn checkout

    Use the svn mv command. Example below:
    svn mv https://dist.apache.org/repos/dist/

    release

    dev/incubator/madlib/1.11-

    -username=<your apache user id>Create a local folder for the release (e.g.

    incubating-rc3/ https://dist.apache.org/repos/dist/release/incubator/madlib/1.11-incubating

  2. Remove old releases from the release and dev dist sitesRetrieve the subversion release incubator madlib repo

    1. Retrieve the subversion release incubator madlib repo if you have not done so already
      Example: svn checkout https://dist.apache.org/repos/dist/release/incubator/madlib/

    2. ) in svn. Move the same files that were part of the release candidate (that got uploaded to the dev dist site and were voted on in the above process) to the release folder on local disk
    3. svn add <release folder>

    4. Commit artifacts:
      Example: svn commit -m 'adding 1.11-incubating release artifacts' --username=<your apache user id>

    Remove old releases from the release and dev dist sites

    1. cd to the directory on local disk where the svn version controlled releases are located
    2. Delete the folders from local working copy copy using svn delete <folder to delete>. 
      E.g. svn delete 1.10.0-incubating/
    3. Commit the deletions: svn commit -m 'removing old releases' --username=<your apache user id>
      Remember to do the above steps for both the "release" and "dev" sites
  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.incubator.apache.org/docs/latest/ 
  4. Announce the release on user@ and dev@ mailing lists. See example email of past announcement.

...