Versions Compared

Key

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

...

  • confirm that the ticket is already in a resolved state on develop
  • confirm the exact commits on develop
  • cherry pick to the release branch
    • git cherry-pick -x <SHA> {SHA} && ./gradleW gradlew build 
    • if fix does not cherry-pick and build cleanly, ask that a PR be submitted against the release branch
  • send a notification to the thread and mark the issue with the correct fixed-in version in Jira:

...

  1. If doing RC2 or later, revert the last temporary commit from geode-examples/gradle.properties and push

    Code Block
    languagebash
    cd geode-examples
    git pull
    git log -1 gradle.properties
    git revert <SHA{SHA from above>above}
    git push


  2. From a checkout of latest geode develop, run the prepare_rc.sh script (a build dir will be created in the current directory, so you may not want to be inside geode when you run it or IntelliJ will freak out).  This script assumes there is a release/X.Y.Z branch pushed to all of the geode repositories (geode, geode-native, geode-examples). It will checkout the tip of that branch for all repos, build them, and copy the artifacts to the build/dist directory. It will also tag the RC in each checkout.  Run this command on a machine with a GUI as you will be prompted to enter PGP passphrase several times and finally 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


  3. The "next steps" printed out at the end of the prepare_rc script will walk you through the remaining steps to stage to nexus (pictured below), publish the release, and send an announcement email.

If there is an older geode staging repository listed (from a previous RC, make sure you drop it. Find "orgapachegeode-####" and click on "Drop"

...