Versions Compared

Old Version 141

changes.mady.by.user Owen Nichols

Saved on

compared with

New Version 142

changes.mady.by.user Owen Nichols

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Click 'Release' in http://repository.apache.org/ (pictured below step 5)
  2. Fork https://github.com/Homebrew/homebrew-core
  3. Make sure you can run docker info and docker images.  On Linux, be sure to add the your user yourself to the docker group to avoid requiring sudo (sudo usermod -aG docker $USER).

  4. 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 'your_40_digit_gpg_key' -g your_github_username


  5. 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.

...

  1. Go to https://issues.apache.org/jira/projects/GEODE?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page
  2.  Click 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) Click Release (note: you must be in the Jira Administrators group to do this, ask on the dev list if you are not).

Transition JIRA issues fixed in this release from Resolved → Closed

...

  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)

...