...
- Checkout the release branch.
Clean the directory
Code Block language bash git clean -fdx
Edit ~/.gradle/gradle.properties with your PGP key and ASF LDAP information:
Code Block language bash signing.keyId=01234567 # Your GPG key ID, as 8 hex digits signing.secretKeyRingFile=/path/to/secring.gpg # Normally in $HOME/.gnupg/secring.gpg nexusUsername=yourname # Your username on Apache's LDAP
Note: If you are using GPG Tools >= 2.1 you likely won't have a secring.gpg file. You can export it with `gpg --export-secret-keys >~/.gnupg/secring.gpg`
- Log in to repository.apache.org and select staging repositories. Find "orgapachegeode-####" and clink on "Drop"
Clean and build the artifacts. Run this command on a machine using GUI as you will be prompted to enter PGP and ASF LDAP password (Apache 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 language bash ./gradlew clean build uploadArchives -Paskpass #Sometime there may be an issue with gradle not picking up the credentials put in ~/.gradle/gradle.properties. # work around is to create a new directory somewhere eg. ~/gradle_home then create a new file in it called gradle.properties # Then run the command as ./gradlew --gradle-user-home=~/gradle_home clean build uploadArchives -Paskpass
Copy and release artifacts to ASF dist repo. DO NOT DELETE THE FOLDERS CREATED IN THIS STEP - THEY ARE NEEDED FOR THE FINAL RELEASE.
Code Block language bash #create a new empty directory svn checkout https://dist.apache.org/repos/dist --depth empty svn update --set-depth infinity --parents dist/dev/geode svn update --set-depth infinity --parents dist/release/geode cd dist/dev/geode # copy the KEYS file from the apache-geode release branch folder in your system. cp ${GEODE_SRC}/KEYS . svn commit -m "Updating Apache Geode KEYS file" mkdir {version}.RC# cp ${GEODE_SRC}/geode-assembly/build/distributions/* {version}.RC# svn add {version}.RC# svn commit -m "Releasing Apache Geode {version}.RC# distribution"
- Verify that all the artifacts have been uploaded to the nexus repository by logging into repository.apache.org and then click on close. Example:
In the release branch folder tag the commit. All Release Candidates start with the number 1 eg. RC1. 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 git tag -s rel/v{version}.RC# -m "Release candidate # for 1.0.0" git push origin rel/v{version}.RC#
Now checkout the repo for geode-examples and create a release branch.
Code Block title Create release branch git checkout -b release/{version}
Update the version number in gradle.properties of geode-examples
Code Block version = 1.7.0 geodeVersion = 1.7.0
In the geode-examples folder, build and run it with the apache-geode version that was uploaded to the ASF dist repo.
Code Block # first build the release artifacts, specifying the RC release location and staging repository ./gradlew -PsignArchives -PgeodeReleaseUrl=https://dist.apache.org/repos/dist/dev/geode/{version}.RC# -PgeodeRepositoryUrl=https://repository.apache.org/content/repositories/orgapachegeode-{NNNN} build runAll #if all tests pass then continue ahead, else kindly fix the issues
If there are no failures, then upload the artifacts to ASF dist repo using the folder created in step 6
Code Block # then upload the release artifacts for distribution # go to the folder created in step 6 and copy the geode-example artifacts to it cd dist/dev/geode cp ${GEODE_EXAMPLES_SRC}/build/distributions/* {version}.RC# svn add {version}.RC#/apache-geode-examples-* svn commit -m "Adding examples to Apache Geode {version}.RC# distribution"
Tag the release candidate in geode-examples.
Code Block # then tag the release candidate commit cd ${GEODE_EXAMPLES_SRC} git tag -s rel/v{version}.RC# -m "Release candidate # for 1.0.0" git push origin rel/v{version}.RC#
Info If you are running on linux, you may see this error message:
error: gpg failed to sign the data
error: unable to sign the tag
If you get that error message, try to sign some random file so that gpg will unlock your keyring. After that the git tag -s should work.
...