Versions Compared

Key

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

...

  1. From one directory above a checkout of latest geode develop, run the prepare_rc .sh script (a release-n.n.n-workspace dir will be created in the current directory).  This script assumes there is a release/X.Y.Z branch pushed to geode, geode-native, and geode-examples.  It will checkout the tip of that branch for all repos, build them, and prepare the artifacts. It will also prepare RC tags in each repository and finally pre-stage to nexus.  Do not run this in a remote shell or headless environment, as a GUI is required to prompt for your PGP GPG passphrase (several times) and your ASF LDAP password (Apache password). Do not include @apache.org in your apache username.

    Code Block
    geode/dev-tools/release/prepare_rc.sh -v version_with_rc -k your_8_digit_key_id -a your_apache_ldap_username


  2. The "next steps" printed out at the end of the prepare_rc script will walk you through the remaining steps to finalize nexus staging (pictured below), publish the release candidate, and send the VOTE email.

...

The last instruction from the prepare_rc script will be to run the commit_rc script.  When that is complete, it will print out the contents of the email for you to send (and also copy it to your clipboard, if you have pbcopy installed).  If you need to re-generate the email for any reason, use geode/dev-tools/release/print_rc_email.sh.  Send the email to the dev@geode.apache.org with subject "[VOTE] Apache Geode <ver>RC<rc>".  Reviewers should be encouraged to describe what they tested, not just give a +1. 

Tally the votes

After the deadline has passed, reply to the VOTE thread with a voting result summary similar to the following (use the PMC roster to determine which votes are binding):

...

Once a release candidate has been approved:

  1. Click 'Release' in http://repository.apache.org/ (pictured in step 3, below)
  2. From from the same directory you were in when you ran the previous release scripts, run the promote_rc .sh script (note: you must be a Geode PMC member to commit to dist/release/geode):

    Code Block
    geode/dev-tools/release/promote_rc.sh -v version_with_rc -k 'your_40_digit_gpg_key' -g your_github_username


  3. The "next steps" printed out at the end of the promote_rc script will walk you through the remaining steps tasks to release the staged artifacts in nexus (pictured below), make the make the brew PR, validate the docker image, update Jira, wait overnight for mirrors to sync, and then finalize the release.

Transition JIRA issues fixed in this release from Resolved → Closed

...