Page History

...

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

   Code Block
   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)
5. Check that the release has propagated to Maven Central.  Sometimes this may take a couple days, it seems?  Two ways to check this are: 
   1. Check for the version you are releasing to appear on https://mvnrepository.com/artifact/org.apache.geode/geode-core
   2. Plus the Examples pipeline for your support branch (e.g. at https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-13-examples)

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

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

...