Versions Compared

Key

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

...

  1. From a checkout of geode, run the prepare_rc.sh script. Run this command on a machine using GUI as you will be prompted to enter PGP key password. You will see messages like "Could not find metadata org.apache.geode:geode-cq/maven-metadata.xml" on your terminal. Ignore them.

    Code Block
    remotes/origin/release/1.9.0
    cd dev-tools/release
    ./prepare_rc.sh -v version_with_rc -k your_8_digit_key_id


    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.

    dickc@lootoo:~/Workspace/geode/develop/gemfire-assembly$ git commit -p
    diff --git a/gradle.properties b/gradle.properties
    index de68acc..2e6a1cb 100755
    --- a/gradle.properties
    +++ b/gradle.properties
    @@ -1,8 +1,8 @@
    group = io.pivotal.gemfire
    -version = 9.9.0-build.9999
    +version = 9.10.0-build.9999
    # Versions of this GemFire assembly, associated geode-support, and bundled greenplum jar
    -geodeSupportVersion = 9.9.0+
    +geodeSupportVersion = 9.10.0+
    greenplumConnectorVersion = 3.+
    minimumGradleVersion = 5.4
    Stage this hunk [y,n,q,a,d,/,s,e,?]? y
    Info

    You may see this error message:

    [develop cb011e4] change defaults to new version 1.10.0
    1 file changed, 2 insertions(+), 2 deletions(-)

    Info

    If you are running on linux, you may see this error message:

    dickc@lootoo:~/Workspace/geode/develop/gemfire-assembly$ git commit -p
    diff --git a/gradle.properties b/gradle.properties
    index de68acc..2e6a1cb 100755
    --- a/gradle.properties
    +++ b/gradle.properties
    @@ -1,8 +1,8 @@
    group = io.pivotal.gemfire
    -version = 9.9.0-build.9999
    +version = 9.10.0-build.9999
    # Versions of this GemFire assembly, associated geode-support, and bundled greenplum jar
    -geodeSupportVersion = 9.9.0+
    +geodeSupportVersion = 9.10.0+
    greenplumConnectorVersion = 3.+
    minimumGradleVersion = 5.4
    Stage this hunk [y,n,q,a,d,/,s,e,?]? y[develop cb011e4] change defaults to new version 1.10.0
    1 file changed, 2 insertions(+), 2 deletions(-)

    error: gpg failed to sign the data

    error: unable to sign the tag

     If you get that error messageIf you do, try to sign some random file so that gpg will unlock your keyring. After that the git tag -s used in prepare_rc.sh should work.


  2. Review the artifacts and revisions under build before moving in to publishing. You should see these directories
    1. geode - This is your geode checkout. It should have a tag for your release, eg rel/v.1.9.0.RC4. Make sure that the revision that was built is correct
    2. geode-examples - The geode examples checkout. Again, check the revision
    3. geode-native - The geode native checkout.
    4. dist   - This is an svn checkout of apache's staging area. It will have artifacts added, but not committed. Review the added artifacts. You should see something like this:

      Code Block
      dist> svn status
      A       dev/geode/1.9.0.RC5
      A       dev/geode/1.9.0.RC5/apache-geode-1.9.0-src.tgz
      A       dev/geode/1.9.0.RC5/apache-geode-1.9.0-src.tgz.asc
      A       dev/geode/1.9.0.RC5/apache-geode-1.9.0-src.tgz.sha256
      A       dev/geode/1.9.0.RC5/apache-geode-1.9.0.tgz
      A       dev/geode/1.9.0.RC5/apache-geode-1.9.0.tgz.asc
      A       dev/geode/1.9.0.RC5/apache-geode-1.9.0.tgz.sha256
      A       dev/geode/1.9.0.RC5/apache-geode-examples-1.9.0.tar.gz
      A       dev/geode/1.9.0.RC5/apache-geode-examples-1.9.0.tar.gz.asc
      A       dev/geode/1.9.0.RC5/apache-geode-examples-1.9.0settings.gradle
      
      add new version to geode-old-versions.tar.gz.sha256
      A       dev/geode/1.9.0.RC5/apache-geode-examples-1.9.0.zip
      A       dev/geode/1.9.0.RC5/apache-geode-examples-1.9.0.zip.asc
      A       dev/geode/1.9.0.RC5/apache-geode-examples-1.9.0.zip.sha256
      A       dev/geode/1.9.0.RC5/apache-geode-native-1.9.0-src.tar.gz
      A       dev/geode/1.9.0.RC5/apache-geode-native-1.9.0-src.tar.gz.asc
      A       dev/geode/1.9.0.RC5/apache-geode-native-1.9.0-src.tar.gz.sha512
      
      


  3. If everything looks good, publish the artifacts to the nexus staging repositories. You will be prompted to enter your ASF LDAP password (Apache password)

    Code Block
    languagebash
    cd build/geode
    ./gradlew  publish -Paskpass -Psigning.keyId=last_8_characters_of_your_gpg_fingerprint -Psigning.secretKeyRingFile=${HOME}.gnupg/secring.gpg -PmavenUsername=your_apache_ldap_username


  4. Verify that all the artifacts have been uploaded to the nexus repository by logging into repository.apache.org and then click on close. Example:
  5. If there is an older geode staging repository listed (from a previous RC, make sure you drop it. Find "orgapachegeode-####" and clink on "Drop"
  6. Publish release artifacts to ASF dist repo. The prepare_rc.sh script should have already added artifacts in dist/dev/geode/full_version_with_rc.

    Code Block
    languagebash
    cd dist/dev/geode
    svn commit -m "Releasing Apache Geode {version}.RC# distribution"


  7. Push the release tags. These were already created (but not pushed) by the prepare_rc.sh script. Be careful as `rel/` folder is protected, once we push the release tag to server, it cannot be modified. Any other change will have to be moved to the next RC number.

    Code Block
    languagebash
    cd build/geode
    git push rel/v[version_with_rc]
    cd ../../build/geode-examples
    git push rel/v[version_with_rc]
    cd ../../build/geode-native
    git push rel/v[version_with_rc]


...