...

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.
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
Create the release branch.
Code Block
title Create release branch
git checkout -b release/{version}
gradle.properties
1. 1. remove -SNAPSHOT in releaseType
docker/Dockerfile
1. 1. Update GEODE_GPG with your GPG fingerprint.
  2. Update GEODE_VERSION with the release version (eg. 1.8.0)

Update the version number in all the expected pom files. Doing it manually takes a lot of time. If you choose to do it I have listed the files below. Otherwise please use the script below to do it.

Info

title	Updating the expected-pom files

- build geode after the version is updated in gradle.properties. NOTE: The build will fail but will have the correct expected-pom.xml files

Code Block

language	bash
title	gradle build

./gradlew clean build -Dskip.tests=true

- Update dependency versions using gradle task updateExpectedPom.

Code Block

language	bash
title	gradle uEP

./gradlew uEP

- Publish the release branch to origin

Code Block

title	Publish the release branch

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

Now checkout the repo for geode-examples and create a release branch.
Code Block
title Create release branch
git checkout develop 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
Commit the version changes and push the release branch of geode-examples
Code Block
git add -p git commit git push origin HEAD

Checkout the repo for geode-native and create a release branch

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

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}

Setting up concourse release pipeline

No Format

$ cd ci/pipelines/meta
$ ./deploy_meta.sh

# You might need fly in your PATH 
# fly target named `concourse.apachegeode-ci.info`
$ fly -t concourse.apachegeode-ci.info login --concourse-url https://concourse.apachegeode-ci.info/

...

Once the release candidate has been approved

Checkout

cd to the release branch for apache geode

Tag and tag the commit with the final version

Code Block
git tag -s rel/v{version} -m "Apache Geode v1.0.0 release" rel/v{version}.RC{latest_rc} git push origin rel/v{version}

Checkout

cd to the release branch for geode-examples

Tag and tag the commit with the final version

Code Block
git tag -s rel/v{version} -m "Apache Geode v1.0.0 release" rel/v{version}.RC{latest_rc} git push origin rel/v{version}

Use svn cd to move the distributions from dev to release. Use the folders created in step 6 of "Creating the release candidate" section.the release branch for geode-native and tag the commit with the final version
Code Block
git tag -s rel/v{version} -m "Apache Geode v1.0.0 release" rel/v{version}.RC{latest_rc} git push origin rel/v{version}

Use svn to move the distributions from dev to release. Use the folders created in step 5 of "Creating the release candidate" section

Code Block

# in the directory created created in step 5 of "Creating the release candidate" section.

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

Update the keys in dist/release.

Code Block

# in the directory created created in step 5 of "Creating the release candidate" section.

cd dist
cpsvn mv dev/geode/{version}.RC#/KEYS release/geode/KEYS{version}
svn commit -m "UpdatingReleasing Apache Geode KEYS{version} filedistribution"

Review

Update the

contents of

keys in dist/release.

Code Block
# in the directory created created in step 5 of "Creating the release candidate" section. cp dev/geode/KEYS release/geode/KEYS svn commit -m "Updating Apache Geode KEYS file"

Review the contents of dist/release. Remove any inactive releases. https://dist. Remove any inactive releases. https://dist.apache.org/repos/dist/release/geode/

Promote the Nexus staging repo → login to repository.apache.org→ Select Staging repositories → Find "orgapachegeode-####" → Click on the Release Button on the toolbar.

Merge release branch to develop and master for apache geode and then delete the release branch

Code Block

git checkout master
git merge -s recursive -Xtheirs release/{version}
git push origin master
  
git checkout develop
git merge -s recursive -Xtheirs release/{version}
git push origin develop
 
git branch -d release/{version}
git push origin --delete release/{version}

Merge release branch to develop and master for geode-examples and then delete the release branch

Code Block

git checkout master
git merge -s recursive -Xtheirs release/{version}
git push origin master
  
git checkout develop
git merge -s recursive -Xtheirs release/{version}
git push origin develop
 
git branch -d release/{version}
git push origin --delete release/{version}

Merge release branch to develop and master for geode-native and then delete the release branch

Code Block

git checkout master
git merge release/{version}
git push origin master
  
git checkout develop
git merge release/{version}
git push origin develop
 
git branch -d release/{version}
git push origin --delete release/{version}

Apache Geode JIRA resolved → closed

...

Upload the docker image to docker hub.

In docker/Dockerfile update the GEODE_GPG with the GPG key you used to sign the release and GEODE_SHA256 with the SHA from https://dist.apache.org/repos/dist/release/geode/{VERSION}/apache-geode-{VERSION}.tgz.sha256 (Replace VERSION with the version you are trying to release).
Follow the instruction present in docker/README.md

Update the brew formula

Code Block

language	bash
title	Homebrew update (MacOS)

# update brew
brew update


# Navigate to homebrew core directory
cd /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core/Formula



# Create a release branch
git checkout -b apache-geode-{version}


#Open apache-geode.rb
vim apache-geode.rb


# add the correct version in lines below 
# in url update "https://www.apache.org/dyn/closer.cgi?path=geode/{version}/apache-geode-{version}.tgz"
# in sha256 update with the SHA256 from https://dist.apache.org/repos/dist/release/geode/{version}/apache-geode-{version}.tgz.sha256


# save the file 


#commit the file - put the right version in below command.
git add .
git commit -a -m "apache-geode {version}"


# Fork git@github.com:Homebrew/homebrew-core.git to your repositories.
#add the remote 
git remote add myfork {your forked homebrew core repo}


#push to your remote forked repo
git push myfork apache-geode-{version}


#create a PR against git@github.com:Homebrew/homebrew-core.git - monitor the the tests in the PR page


#test it locally.
git checkout master


git merge apache-geode-{version}
brew install --build-from-source apache-geode


#check for gfsh version - should be the released version
gfsh version


# uninstall apache-geode
brew uninstall apache-geode


#reset master to origin
git reset --hard origin/master

Publish javadocs and documentation to the website

...

Apache Geode JIRA resolved → closed

Mark the version as released in Jira: go to https://issues.apache.org/jira/projects/GEODE?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page and click on the ... to get the Actions pop-up menu and click Release.
List all the JIRAs with fix version as the release version and status as resolved.
Image Added

Using bulk operations → transition to closed state.

Image Added

Image Added

Image Added

Image Added

* this is a good time to go home / take a nap / finish it tomorrow. mirror sites can take 8-24 hours to sync, and the below docker and brew and announce steps depend on most or all mirrors being up-to-date.*

Upload the docker image to docker hub.

docker/Dockerfile
1. 1. Update GEODE_GPG with your GPG fingerprint.
  2. Update GEODE_VERSION with the release version (eg. 1.8.0)
  3. Update GEODE_SHA256 with the SHA from https://dist.apache.org/repos/dist/release/geode/{VERSION}/apache-geode-{VERSION}.tgz.sha256 (Replace VERSION with the version you are trying to release).
Check these changes in to the release branch. If for some reason you have already merged the release branch to master and deleted it, check the changes in to master.
Follow the instruction present in docker/README.md
Note that you may see a 404 error during the docker build process, because it tries a mirror first before falling back to the primary download site, and some mirror sites take 8-24 hours to sync. As long as the docker build completes successfully you're ok.

Update the brew formula

Code Block

language	bash
title	Homebrew update (MacOS)

# update brew
brew update


# Navigate to homebrew core directory
cd /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core/Formula



# Create a release branch
git checkout -b apache-geode-{version}


#Open apache-geode.rb
vim apache-geode.rb


# add the correct version in lines below 
# in url update "https://www.apache.org/dyn/closer.cgi?path=geode/{version}/apache-geode-{version}.tgz"
# in sha256 update with the SHA256 from https://dist.apache.org/repos/dist/release/geode/{version}/apache-geode-{version}.tgz.sha256


# save the file 


#commit the file - put the right version in below command.
git add .
git commit -a -m "apache-geode {version}"


# Fork git@github.com:Homebrew/homebrew-core.git to your repositories.
#add the remote 
git remote add myfork {your forked homebrew core repo}


#push to your remote forked repo
git push myfork apache-geode-{version}


#create a PR against git@github.com:Homebrew/homebrew-core.git - monitor the the tests in the PR page


#test it locally.
git checkout master


git merge apache-geode-{version}
brew install --build-from-source apache-geode


#check for gfsh version - should be the released version
gfsh version


# uninstall apache-geode
brew uninstall apache-geode


#reset master to origin
git reset --hard origin/master

The brew team usually accepts the PR within 24 hours. Note: they may close it without merging. Either way, check that latest version has been added to brew by doing brew install apache-geode.

Publish javadocs and documentation to the website

Build website from sources as described in geode-site/website/README.md.
In the generated site, create the directory geode-site/content/releases/latest.
Obtain a copy of the javadoc directory from the binary build and put it in the geode-site/content/releases/latest directory (link from the website's Docs landing page points to ../releases/latest/javadoc).
Deploy the generated site by checking it into the asf-site branch of the apache-geode repo.

Merge to master

Merge release branch to master for apache geode and then delete the release branch

Code Block

git fetch --all
git checkout release/1.9.0
git merge -s ours origin/master -m "Merging release/1.9.0 into master"
git checkout master
git merge release/1.9.0
git push origin master
  
git branch -D release/{version}
git push origin --delete release/{version}

Merge release branch to master for geode-examples and then delete the release branch, using same commands as above
Merge release branch to master for geode-native and then delete the release branch, using same commands as above

Sending the announce mail.

***

...

Sending the announce mail.

Important: Send the email from an apache email ID. ***

No Format

The Apache Geode community is pleased to announce the availability of
Apache Geode {version}.
Apache Geode is a data management platform that provides a database-like
consistency model, reliable transaction processing and a shared-nothing
architecture to maintain very low latency performance with high concurrency
processing.
Geode {version} contains a number of improvements and bug fixes. It includes performance improvements in OQL order-by and distinct queries in client/server when security is enabled. New GFSH commands were added to get/set cluster config and to destroy gateway receivers. A new post processor was added to the new client protocol. Pulse now supports legacy SSL options. Auto-reconnecting members no more reuse old addresses and IDs. Duplicated or member-specific receivers are removed from cluster config during rolling upgrades. Users are encouraged to upgrade to the latest release.
For the full list of changes please review the release notes:
https://cwiki review the release notes:
https://cwiki.apache.org/confluence/display/GEODE/
Release+Notes#ReleaseNotes-{version}
The release artifacts can be downloaded from the project website:
http://geode.apache.org/releases/
The release documentation is available at:
http://geode.apache.org/confluencedocs/display/GEODE/
Release+Notes#ReleaseNotes-{version}
The release artifacts can be downloaded from the project website:
http://geode.apache.org/releases/
The release documentation is available at:
http://geode.apache.org/docs/guide/{version eg. in the format as 17 or 18 or 19}/about_geode.html
We would like to thank all the contributors that made the release possible.
Regards,
{Release Manager} on behalf of the Apache Geode team

Post release:

Add the released version to geode-old-versions/build.gradle

Eg.

guide/{version eg. in the format as 17 or 18 or 19}/about_geode.html
We would like to thank all the contributors that made the release possible.
Regards,
{Release Manager} on behalf of the Apache Geode team

Post release:

Add the released version to geode-old-versions/build.gradle

Eg.

Code Block
addOldVersion('test160', '1.6.0', true)

Destroy the concourse release pipeline (details tbd)

No Format

$ cd ci/pipelines/meta
$ ./destroy_meta.sh

# You might need fly in your PATH 
# fly target named `concourse.apachegeode-ci.info`
$ fly -t concourse.apachegeode-ci.info login --concourse-url https://concourse.apachegeode-ci.info/

Code Block

addOldVersion('test160', '1.6.0', true)

Space shortcuts

Page tree

Versions Compared

Old Version 43

New Version 44

Key

Apache Geode JIRA resolved → closed

Upload the docker image to docker hub.

Update the brew formula

Publish javadocs and documentation to the website

Apache Geode JIRA resolved → closed

Using bulk operations → transition to closed state.

Image Added

Image Added

Image Added

Image Added

* this is a good time to go home / take a nap / finish it tomorrow. mirror sites can take 8-24 hours to sync, and the below docker and brew and announce steps depend on most or all mirrors being up-to-date.*

Upload the docker image to docker hub.

Update the brew formula

Publish javadocs and documentation to the website

Merge to master

Sending the announce mail.

Sending the announce mail.

Post release:

Post release:

Space shortcuts

Page tree

Page History

Versions Compared

Old Version 43

New Version 44

Key

Apache Geode JIRA resolved → closed

Upload the docker image to docker hub.

Update the brew formula

Publish javadocs and documentation to the website

Apache Geode JIRA resolved → closed

Using bulk operations → transition to closed state.Image AddedImage AddedImage AddedImage Added

*** this is a good time to go home / take a nap / finish it tomorrow. mirror sites can take 8-24 hours to sync, and the below docker and brew and announce steps depend on most or all mirrors being up-to-date.***

Upload the docker image to docker hub.

Update the brew formula

Publish javadocs and documentation to the website

Merge to master

Sending the announce mail.

Sending the announce mail.

Post release:

Post release:

Using bulk operations → transition to closed state.

Image Added

Image Added

Image Added

Image Added

* this is a good time to go home / take a nap / finish it tomorrow. mirror sites can take 8-24 hours to sync, and the below docker and brew and announce steps depend on most or all mirrors being up-to-date.*