This article contains all the steps required to release Apache Geode. 

Before you begin

Software dependencies

1. git →  https://git-scm.com/downloads
2. docker → https://docs.docker.com/docker-for-mac/install/ svn → [on Mac, install command line tools → https://stackoverflow.com/questions/9329243/xcode-install-command-line-tools]
3. gpg tools → https://gpgtools.org
4. java JDK8 → https://adoptopenjdk.net Make sure you have the latest patch release of OpenJDK 1.8.0 (not Oracle JDK).
5. Homebrew (optional) → https://brew.sh/
6. svn → [on Mac, brew install svn]
7. fly → use platform-appropriate download link in bottom right corner of https://concourse.apachegeode-ci.info. Do it this way, not with homebrew, so you get the version that matches concourse.
8. cmakecmake, doxygen, and openssl - install using an appropriate package manager, e.g. on Mac: brew install doxygen && brew install cmake && brew install openssl
9. jinja → pip3 install Jinja2
10. PyYAML → pip3 install PyYAML
11. text editor (vi or whatever you prefer)
12. web browser

...

Announce intent to branch

Geode cuts release branches on a time-based schedule (Monday on or after Feb 1, May 1, Aug 1, Nov 1).  About a week before, send a [DISCUSS] email to dev@geode.apache.org informing developers that a new release branch is about to be created.  Remind the community that only critical fixes will be allowed once the release branch is created, so it is helpful to have develop as stable as possible before branching.

Also ask the community to confirm that the Geode LICENSE and NOTICE files accurately reflect what is on develop. 

Branching for release

Create the release branch

Terminology

A major release is a version x.0.0 and allows/implies breaking changes, removal of deprecated methods, changes to minimum JDK, etc. 

A minor release is a version x.y.0 where y > 0 and typically allows/implies new features.

A patch release is a version x.y.n where n > 0 and should contain a limited number of critical fixes only.

Except where noted, all instructions in this guide apply to all three types of releases.  Dev list proposals for patch releases may be made at any time since the branch already exists, however some planning ahead is helpful for major or minor releases. since it is usually desirable to cut the branch a couple months in advance. 

Propose cutting a support branch (major/minor only)

Send a [DISCUSS] email to dev@geode.apache.org proposing that a new support branch be created.

Review LICENSE and NOTICE files

Confirm that the Geode LICENSE and NOTICE files on develop are accurate (ask for help on the dev list if needed).  This is best done before cutting the branch, otherwise be sure to backport any changes to the support branch as well.

1. cd .. && ./geode/dev-tools/release/license_review.sh -v HEAD -p 1.12.0 (replace 1.12.0 with the version of the previous release) to check the LICENSE files for missing dependencies or outdated versions and compare dependencies against a previous release.  If any dependencies were removed, manually check for stale references in LICENSE or NOTICE files that can be removed.  If new dependencies were added that have Apache 2.0 License, add them to the license_review script's isApache2 function.  If a new 3rd-party .jar is now appearing in the binary distribution, update geode-assembly/src/main/dist/LICENSE appropriately.   If new 3rd-party intellectual property was checked into the source tree (e.g. a javascript library), update both LICENSE and geode-assembly/src/main/dist/LICENSE.

Branching for release

Create the support branches (major/minor only)

1. From one directory above a checkout of latest geode develop, run the create_support_branches script.  This will create branches on all projects and update version numbers appropriately, and guide you though creating the support pipeline, updating Jira, and creating a PR to bump develop to the next version.

   Code Block
   language bash
   cd .. geode/dev-tools/release/create_support_branches.sh -v 1.13 -g your_github_username

   
   

2. Review the benchmark baseline on the support branch.  It should usually be {previous release} 

   See ci/pipelines/shared/jinja.variables.yml around line 20 (under benchmarks:)

   Code Block
   language yml
   baseline_version: '1.12.0'

   
   

3. Send email to dev@geode.apache.org informing the creation of the support branch and any rules for backporting changes to the branch.

   No Format
   Hello Geode Dev Community, We have created a new support branch for Apache Geode {x.y.0} - "support/{x.y}" Please focus your acceptance testing on this branch and raise any concerns in the next few weeks. If any changes are needed please add blocks-{x.y.0} label in Jira and create a PR against support/{x.y}. After some quiet period we will prepare a release candidate and begin voting upon it

4. 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.
5. Ensure that all JIRA tickets mentioned in commits (since the last release branch was cut) are marked as Resolved in JIRA.  If not, ask assignees if there is still more work to be done.
6. 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 mark it Resolved or  increment the fix version.

Create the release branch (from HEAD should be fine, or if necessary you can specify a particular SHA, such as the last commit that passed the develop pipeline successfully)

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

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

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

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

10. Update the version number in all the expected pom files:

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

     

11. 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: '' benchmark_branch: develop

    Publish the release branch to origin

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

    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}

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

    No Format
    version = 1.7.0 geodeVersion = 1.7.0

    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

    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

    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}

    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

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

Begin preparing release documentation

...

Also write up a short paragraph on what was added to the release. This will need to go with the final announce email. Sample:

Geode 1.7.0 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.

Bump the version of the develop branch

You will need to checkout the develop branch of geode and geode-examples.

...

1. 1. update the version property to the next release version and ensure that it has -SNAPSHOT on the end. (for example: if you created release branch for 1.8.0 update version number to 1.9.0-RELEASE on the develop branch)

...

Add the new ordinal for the new version

//Add 5 to the previous ordinal
private static final byte GEODE_1_9_0_ORDINAL = 100;

Add the new version 

public static final Version GEODE_1_9_0 =
      new Version("GEODE", "1.9.0", (byte) 1, (byte) 9, (byte) 0, (byte) 0, GEODE_1_9_0_ORDINAL);

Set the current version to the new version

public static final Version CURRENT = GEODE_1_9_0;

Update the highest version

public static final int HIGHEST_VERSION = 105;

...

Add the next version to addCommands

allCommands.put(Version.GEODE_1_9_0, geode18Commands);

...

Update the expected-pom.xml files

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

Review the benchmark baseline.  In theory this could be updated to the new release branch, but the highwater tag is preferable.

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

 benchmarks:
   baseline_branch: develop/highwater
   baseline_version: ''
   benchmark_branch: develop

Publish the develop branch to origin

git add .
git commit -a -m "Upgraded version number for releasing 1.x.x"
pit push origin develop

...

Plus the BumpMinor task to increment the concourse version in the apache-geode concourse pipeline at: 
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main?groups=Semver%20Management
(if you do not have concourse permissions to plus jobs, ask on the dev list)

Update the version and geodeVersion in gradle.properties file of the geode-example develop branch to the next release version

git checkout develop
version = 1.9.0-SNAPSHOT
geodeVersion = 1.9.0-SNAPSHOT
git add -p
git commit
git push origin HEAD

...

In Jira, add new version of develop: go to https://issues.apache.org/jira/projects/GEODE?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page and fill in the new version and click Add (note: you must be in the Jira Administrators group to do this, ask on the dev list if you are not).

Creating a Release Candidate

Accept critical fixes to the release branch

It is expected that some stabilization work may be needed once the release branch is cut.

Proposals to bring completed and tested fixes from develop to the release branch may be made to the dev list.  The release manager may join the conversation if needed to remind the community of the process, for example: 

Hi <thread participant(s)>, thank you for bringing your concern.

Geode's release process dictates a time-based schedule to cut release branches.  Once cut, the “critical fixes” rule allows critical fixes to be brought to the release branch by proposal on the dev list.

If there is consensus from the Geode community that your proposed change satisfies the “critical fixes” rule, I will be happy to bring it to the {version} release branch.

Regards
{Release Manager}

If three +1's are received and no minus 1's, the release manager should:

• 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} && ./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:

There appears to be consensus that this is a critical fix.

The following commit has been brought into release/{version} as the critical fix for GEODE-XXXX:

git cherry-pick -x {SHA}

GEODE-XXXX has been marked as 'resolved in' {version}.

Regards
{Release Manager}

Please note that there is no required voting period to bring a critical fix; it can be merged immediately upon getting 3 +1's.  However, the release manager should monitor and revert it from the release branch if it causes test problems, or further discussion of the fix leads to any "minus 1".

Create the release candidate

From one directory above a checkout of latest geode develop, run the prepare_rc script (a release-n.n.n-workspace dir will be created in the current directory).  This script assumes there is a release/X.Y.Z branch pushed to geode, geode-native, and geode-examples.  It will checkout the tip of that branch for all repos, build them, and prepare the artifacts. It will also prepare RC tags in each repository and finally pre-stage to nexus.  Do not run this in a remote shell or headless environment, as a GUI is required to prompt for your GPG passphrase (several times) and your ASF LDAP password (Apache password). Do not include @apache.org in your apache username.

geode/dev-tools/release/prepare_rc.sh -v version_with_rc -k your_8_digit_key_id -a your_apache_ldap_username

...

The "next steps" printed out at the end of the prepare_rc script will walk you through the remaining steps to finalize nexus staging (pictured below), publish the release candidate, and send the VOTE email.

...

Image Removed

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

Image Removed

Sanity Check

Before giving the RC to the community to validate, make an rc pipeline to validate that the artifacts are viable:

geode/dev-tools/release/deploy_rc_pipeline.sh -v version_without_rc

Send out an email announcing the RC

The last instruction from the prepare_rc script will be to run the commit_rc script.  When that is complete, it will print out the contents of the email for you to send (and also copy it to your clipboard, if you have pbcopy installed).  If you need to re-generate the email for any reason, use geode/dev-tools/release/print_rc_email.sh.  Send the email to the dev@geode.apache.org with subject "[VOTE] Apache Geode <ver>RC<rc>".  

Tally the votes

After the deadline has passed, reply to the VOTE thread with a voting result summary similar to the following (use the PMC roster to determine which votes are binding):

It's past the announced deadline and we have enough votes to close the vote.

Voting status
==========
+1: 3 binding votes
* Name (PMC member)
* Name (PMC member)
* Name (PMC member)
* Other Name
* Other Name

+0: zero votes

-0: zero votes

-1: zero votes

The voting meets the requirements of at least 3 PMC members with +1 votes and has the required majority of +1 votes.
Apache Geode {ver}.RC{n} passed the vote and we will finalize the release shortly.

Thanks everyone for the great work!

-{Release Manager}

If not enough votes are received, the release manager may, at their discretion, extend the voting deadline, or close the vote and start a DISCUSS thread on whether to abandon the release or try again.

If the voting is successful, proceed to the next section.  If showstopper issues were raised, create a new release candidate.  If the release is to be abandoned, destroy the pipeline, release branch, and staged artifacts in nexus and svn.

Finalizing the Release

Promote the release candidate to final release

Once a release candidate has been approved:

...

From the same directory you ran the previous release scripts, run the promote_rc script (note: you must be a Geode PMC member to commit to dist/release/geode):

geode/dev-tools/release/promote_rc.sh -v version_with_rc -k 'your_40_digit_gpg_key' -g your_github_username

...

1. 
   

2. For the duration of the release process, continue to monitor the new release pipeline and address any issues that may arise, including analyzing any test failures (ask for volunteers on the dev list to investigate any failures you are unsure of).

Bump the version of the develop branch (major/minor only)

1. The create_support_branches script already walked you through creating the PR for this, adding the new version to Jira, and bumping the pipeline version on develop.  (note: you must be in the Jira Administrators group to see the Add button in Jira; request permission on the dev list if you don't see it).

Validate Fix Versions in JIRA

There are two parts to this audit:

1. Does every commit since the last release have a corresponding Jira ticket marked as Fixed in this version?
2. Can every Jira ticket marked as fixed in this version be traced to a commit in this support branch since the last release?

To help automate the process of identifying commits and tickets in need of review, you may find this script useful, or create your own script.

Tips:

• If a Jira ticket is fixed on develop AND cherry-picked to a support branch, it should list both fix versions.
• If a Jira ticket is fixed by way of another commit or Jira ticket, there should be a comment detailing this.
• If a Jira ticket is partially fixed but there is more work to be done in the next release, splitting into two tickets may be the best way to represent that.
• Don't forget about geode-native.  It's a separate git repository but uses GEODE Jira tickets and is released as part of Geode.
• Be mindful of revert commits.
• Be mindful of Jira tickets resolved as "Won't Fix", "Duplicate" etc.
• Be mindful of Jira tickets that were re-opened, but the Fixed version was never cleared.
• For changes that came in close to the time a support branch was cut, double-check whether the fix actually made it onto the branch.  The list of release start dates can be helpful, but checkout the release tag to confirm for certain. 
• When in doubt, reach out to people that have been involved the with ticket to confirm its status.  Many times they just forgot to marked it fixed when their PR got merged, or forgot to fill in the fixed version.

Begin preparing release documentation

1. Start preparing the release docs at Release Notes. Ask the community for suggestions on fixes and features to highlight, or go through the commits yourself and choose 5-10 items of interest. 

2. Also write up a short paragraph on what was added to the release. This will need to go with the final announce email. Sample:

   
   

   No Format

   Geode 1.13.0 contains a number of improvements and bug fixes. Changes since last release: - 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 longer 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.

   
   

Creating a Release Candidate

Accept critical fixes to the support branch

It is expected that some stabilization work may be needed once the support branch is cut.  This phase may be very short or very long until a Release Candidate is proposed.

The Release Manager will set the rules for backporting changes to the support branch.  For example, they may stipulate critical fixes only and/or require a dev list proposal and/or require a PR against the support branch and/or require a label to be added in Jira. In all cases, fixes need to be made on develop first, then backported.

By some method, determine when all fixes are in.  This might involve one or more of:

• checking for Jira tickets tagged as blockers that are not yet delivered
• checking for PRs that are not yet merged
• checking on the dev list for proposals
• waiting for any test failures or other concerns to be resolved
• waiting for some quiet period of no new blocker, PRs, proposals, or concerns.

When all signs point to "go", you can either just create the RC and propose it in one email, or if there is any uncertainly, start a dev list discussion first. 

Create the release candidate

1. From one directory above a checkout of latest geode develop, run the prepare_rc script (a release-n.n.n-workspace dir will be created in the current directory).  This script will do a fresh checkout of the support branch for all repos, build them, and prepare the artifacts. It will also prepare RC tags in each repository and finally pre-stage to nexus.  Do not run this in a remote shell or headless environment, as a GUI is required to prompt for your GPG passphrase (several times) and your ASF LDAP password (Apache password). Do not include @apache.org in your apache username.  If your are not a PMC member, when prompted for SVN password, hit enter and ask a PMC member to enter their username and password, otherwise you will not be able to make the final release later.

   Code Block
   geode/dev-tools/release/prepare_rc.sh -v 1.13.0.RC1 -k last_8_digits_of_your_gpg_key -a your_apache_ldap_username

   
   

2. The "next steps" printed out at the end of the prepare_rc script will walk you through the remaining steps to finalize nexus staging (pictured below), publish the release candidate, and send the VOTE email.

3. Image Added

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

Image Added

Sanity Checks

1. As instructed by commit_rc, before giving the RC to the community to validate, make an rc pipeline to validate that the artifacts are viable (do this in a separate terminal window as it can be quite verbose):

geode/dev-tools/release/deploy_rc_pipeline.sh -v 1.13

2. wait for all jobs to turn green (about 1-2 hours)

Send out an email announcing the RC

The last instruction from the prepare_rc script will be to run the commit_rc script.  When that is complete, it will print out the contents of the email for you to send (and also copy it to your clipboard, if you have pbcopy installed).  If you need to re-generate the email for any reason, use geode/dev-tools/release/print_rc_email.sh.  

Click on every link to validate (especially release notes!), then send the email to the dev@geode.apache.org with subject "[VOTE] Apache Geode <ver>.RC<n>".

The voting deadline should be at least 72 hours in the future (typically 3pm 5 days hence if there is a weekend).  For emergency patch releases, an expedited voting deadline of as little as 24 hours may be used.

Tally the votes

After the deadline has passed, reply to the VOTE thread with a voting result summary similar to the following (use the PMC roster to determine which votes are binding):

It's past the announced deadline and we have enough votes to close the vote.

Voting status
==========
+1: 3 binding votes
* Name (PMC member)
* Name (PMC member)
* Name (PMC member)
* Other Name
* Other Name

+0: zero votes

-0: zero votes

-1: zero votes

The voting meets the requirements of at least 3 PMC members with +1 votes and has the required majority of +1 votes.
Apache Geode {ver}.RC{n} has passed the vote and we will finalize the release shortly.

Thanks everyone for the great work!

-{Release Manager}

If not enough votes are received, the release manager may, at their discretion, extend the voting deadline, or abandon the release.

If the voting is successful, proceed to the next section.  If showstopper issues were raised, create a new release candidate.  If the release is to be abandoned, destroy any staged artifacts in nexus and svn.

Finalizing (shipping) the Release

Promote the release candidate to official release

Once a release candidate has been approved:

1. Click 'Release' in http://repository.apache.org/ (pictured below step 7)
2. Make sure you have forked https://github.com/Homebrew/homebrew-core (click the Fork button in top-right corner)
3. Make sure you have forked https://github.com/apache/geode-native
4. Make sure you have forked https://github.com/apache/geode
5. Make sure you can run dockerinfo and dockerimages.  On Linux, you may need to add sudo before each docker command in the promote_rc script and/or sudo usermod -aG docker $USER

6. From the same directory you ran the previous release scripts, run the promote_rc script (note: you must be a Geode PMC member to svn commit to dist/release/geode):

   Code Block
   geode/dev-tools/release/promote_rc.sh -v 1.13.0.RC1 -k last_8_digits_of_your_gpg_key -g your_github_username

   
   

7. The "next steps" printed at the end of the promote_rc script will walk you through the remaining tasks to validate the docker image, update Jira, make the brew PR, then finalize the release, followed by the contents of the announce email (also copied to your clipboard, if you have pbcopy installed).  You can also (re)generate the email later using geode/dev-tools/release/print_announce_email.sh.  It's ok to start on the steps below while you are waiting for promote_rc to finish.
   
   Image Added

Mark the version as released in Jira

1. Go to https://issues.apache.org/jira/projects/GEODE?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page
2. Click on the ... to get the Actions pop-up menu for the version you are releasing
3. Click Release (note: you must be in the Jira Administrators group to do this, ask on the dev list if you are not).
4. While you're in there, add the next patch release (i.e. if you are releasing x . y . n, add x . y . n+1) 

Transition JIRA issues fixed in this release from Resolved → Closed

1. List all the JIRAs with fix version as the release version and status as resolved.
   Image Added
   
   
   
2. Using bulk operations → transition to closed state.
   
   
   Image Added
   
   Image Added
   
   Image Added
   
   Image Added
   
   

Publish to GitHub

1. Go to https://github.com/apache/geode/tags 

2. Locate (but do not click on) the row with the final release tag (e.g. rel/v1.13.0)

3. Click on the 2nd "..." menu (the one to the right of the Verified bubble), then Create release.

4. "Existing tag" should be selected.
5. Fill in Release Title e.g. Apache Geode 1.13.0.

6. Describe the release:

   1. Copy the summary sentence from the release notes.

   2. Add the SHA256 (e.g. from the directory you ran the release scripts, cat release-1.13.0-workspace/geode/geode-assembly/build/distributions/apache-geode-1.13.0.tgz.sha256).

   3. Add a link to the release notes.  Example: 

      Code Block
      title Sample Release Description
      This release contains some new gfsh commands and support for SNI as well as a number of improvements and bug fixes. sha256 for apache-geode-1.13.0.tgz is 8caf6dcafa5c6bb7c10dc7d512d0569dd16e463e01c18997118e20a5f43e6097 See full release notes at https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.13.0

      
      

7. Click where it says "Attach binaries" and upload the Apache Geode .tgz (found in the directory you ran the release scripts under release-1.13.0-workspace/geode/geode-assembly/build/distributions/apache-geode-1.13.0.tgz)
8. Click the green Publish Release button. 

Publish javadocs and documentation to the website

Ask on the dev list if you need help with these steps.

1. Keep only the latest patch release of each of the 3 most recent minors (including the one you're about to release) on https://geode.apache.org/releases/

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

Final checks

(note: These steps are also covered by the "Final steps" printed at the end of promote_rc)

1. Confirm that your brew PR has been merged or closed and brew install apache-geode picks up the new release.  Note: this may take overnight...no need to hold the release announcement just for brew.

   Code Block
   brew uninstall apache-geode brew install apache-geode gfsh version

   
   

2. Check that docs for the version you are releasing appear on https://geode.apache.org/docs/
3. Check that download detail for the version you are releasing appear on https://geode.apache.org/releases/
4. Check that the release tag appears as "Verified" in https://github.com/apache/geode/tags (if not, see last step in Permissions and Keys)

Ask for a volunteer to update dependencies on develop (major/minor only)

Now is the best time to bump dependency versions on develop for the various 3rd-party libraries used by Geode. Start a DISCUSS thread asking for a volunteer to lead this effort.

To:  dev@geode.apache.org

Subject: [DISCUSS] Volunteer to update 3rd-party libraries used by GEODE

Hello Apache Geode Community, 

It's time to update the 3rd-party libraries used by GEODE.  We need a volunteer to take on this responsibility.

https://github.com/apache/geode/blob/develop/dev-tools/dependencies/README.md describes how to carry out this task.

It would be awesome to get this done within the next few weeks, to allow plenty of time to shake out any issues before the next release.

Regards,
{Release Manager} on behalf of the Apache Geode team

Remove old unsupported branches (major/minor only)

Geode's N-2 support policy allows patch releases to be proposed for its 3 most recent minors, e.g. on the day 1.15.0 is released, 1.12 would become no longer supported.  But this is not set in stone, so it's probably wise to start a discussion on the dev list before just running this command!

1. remove 1.<N-3> support branch, pipelines and RC tags:

geode/dev-tools/release/end_of_support.sh -v 1.{N-3}

Note tha end_of_support is a destructive command.  It will prompt you to continue, then will delete the branch and pipeline.  If run by accident, these can be restored by re-flying the pipeline and re-pushing the branch (if you or someone has an up-to-date local copy, otherwise google git reflog for more ways to recover a deleted branch).

Send the announce mail

The template for this email was output at the end of promote_rc, or you can re-generate it using geode/dev-tools/release/print_announce_email.sh.  Consider customizing the generated text if there are more upcoming releases (or even waiting and combining the announcements) or if there are notable fixes worth highlighting after the generic "contains a number of fixes".

*** Important: Send the email from your apache email ID*** (otherwise announce@apache.org will bounce. See https://infra.apache.org/committer-email.html for how to send email from your apache email address)

*** Important: Send the email as plain text***(otherwise announce@apache.org will reject the email.  If using gmail, at the bottom of the compose window, click the three-dot menu then click Plain text mode)

Example:

Transition JIRA issues fixed in this release from 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 (note: you must be in the Jira Administrators group to do this, ask on the dev list if you are not).

...

Wait for mirror sites to sync

*** this is a good time to call it a day...mirrors take overnight to sync the new release ***

Finalize the release

Confirm that your brew PR has been closed and brew install apache-geode picks up the new release.  

brew install apache-geode
gfsh version

...

geode/dev-tools/release/finalize_release.sh -v version_without_rc

The "next steps" printed out at the end of the finalize_release script will walk you through the remaining steps update mirror links, publish docs site, and send the official release announcement.

Publish javadocs and documentation to the website

Ask on the dev list if you need help with these steps.

...

Update links to previous releases that appear on https://geode.apache.org/releases/.  The finalize_release script may have removed some old version from the mirror site, if so, the links on the "downloads" web page should be changed to point to the archive site instead, i.e.

1. change the links for any old versions removed by finalize_release.sh that contain closer.cgi to archive, e.g.:
   1. before: http://apache.org/dyn/closer.cgi/geode...
   2. after: http://archive.apache.org/dist/geode...
2. change the .asc/.sha256 links like this:
   1. before: https://www.apache.org/dist/geode...
   2. after: https://archive.apache.org/dist/geode...

...

Update dependencies

Now is the best time to bump dependency versions on the various 3rd-party libraries used by Geode.  Start a DISCUSS thread asking for a volunteer to lead this effort.

...

To:  user@geode.apache.org, announce@apache.org, dev@geode.apache.org

Subject: [ANNOUNCE] Apache Geode 1.9.0*** Important: Send the email from your apache email ID*** (otherwise announce@apache.org will bounce. See https://reference.apache.org/committer/email for how to send email from your apache email address)Geode {version e.g. 1.13.0}

The Apache Geode community is pleased to announce the availability of
Apache Geode {version e.g. 1.13.0}.

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 e.g. 1.13.0} 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.apache.org/confluence/display/GEODE/
Release+Notes#ReleaseNotes-{version e.g. 1.13.0}

The release artifacts can be downloaded from the project website:
httphttps://geode.apache.org/releases/

The release documentation is available at:
httphttps://geode.apache.org/docs/guide/{version eg. in the format as 17 or 18 or 19113}/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

...