Page History

...

1. Check for the most recent develop SHA that passes all the tests and contains all the features / bug fixes that need to go into the release at https://concourse.apachegeode-ci.info/beta/teams/main/pipelines/develop/jobs/UpdatePassingRef.
2. Ensure in JIRA, that all tickets with {version} as the fix version are either closed or resolved. If not inform the the assignees to either resolve/close it or if not fixed then increment the fix version in the ticket

3. Create the release branch.

   Code Block
   language bash
   git checkout develop git checkout -b release/{version}

   
   

4. Update the version number in gradle.properties (and remove -SNAPSHOT)

5. Update the version number in ci/pipelines/geode-build/jinja.template.yml

6. Change SNAPSHOT to "" for SEMVER_PRERELEASE_TOKEN in ci/pipelines/meta/meta.properties

7. Update the version number in all the expected pom files use these steps:

   Code Block
   language bash
   ./gradlew clean ./gradlew build -Dskip.tests=true #note: ok if build fails expected pom test ./gradlew updateExpectedPom

    

8. Review the benchmark baseline.  It should be the more recent of {previous release} or develop/highwater.  branch should stay as develop even for release branches.  Note: as the release progresses, consider creating and using a dedicated version/highwater tag on the release branch.

   See ci/pipelines/shared/jinja.variables.yml around line 19:

   Code Block
   language yml
   benchmarks: baseline_branch: develop/highwater baseline_version: '' branch: develop

   
   

9. Publish the release branch to origin

   Code Block
   language bash
   git add . git commit -a -m "Upgraded version number for releasing {version}" pit push origin release/{version}HEAD

   
   

10. Now checkout the repo for geode-examples (apache/geode-examples.git) and create a release branch.

    Code Block
    language bash
    git clone git@github.com:apache/geode-examples.git git checkout develop origin/develop git checkout -b release/{version}

    
    

11. Update the version number in gradle.properties of geode-examples and remove -SNAPSHOT

    No Format
    version = 1.7.0 geodeVersion = 1.7.0

    
    

12. Commit the version changes and push the release branch of geode-examples

    
    

    Code Block
    language bash
    git add -p git commit git push origin HEAD

    
    

13. Checkout the repo for geode-native (apache/geode-native.git) and create a release branch

    
    

    Code Block
    language bash
    git checkout develop git checkout -b release/{version} git push origin HEAD

    
    

14. Send email to dev@geode.apache.org informing the creation of the release branch and requesting feedback.

    No Format
    Hello Geode Dev Community, We have created a new release branch for Apache Geode {version} - "release/{version}" Please do review and raise any concern with the release branch. If no concerns are raised, we will start with the voting for the release candidate soon. Regards {Release Manager}

    
    

15. Create the concourse release pipeline.

    Code Block
    language bash
    fly -t concourse.apachegeode-ci.info login --concourse-url https://concourse.apachegeode-ci.info/ cd ci/pipelines/meta ./deploy_meta.sh

    
    

16. Monitor the new release pipeline and resolve any issues that may arise. 

...

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.

   Info
   You may see this error message: error: gpg failed to sign the data error: unable to sign the tag If 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.0.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
   language bash
   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
   language bash
   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
   language bash
   cd build../../../geode git push origin rel/v[version_with_rc] cd ../../build/geode-examples git push origin rel/v[version_with_rc] cd ../../build/geode-native git push origin rel/v[version_with_rc]

   
   

Send out an email announcing the RC

...