Page History

...

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

2. wait for all jobs to turn green

3. In the next step will send an email...be sure to click EVERY link in the email before sending!

(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.  Validate (visit) all links 

Be sure to click on EVERY link to validate, then send the email to the dev@geode.apache.org with subject "[VOTE] Apache Geode <ver>RC<rc><ver>.RC<n>".  

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}

...

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.  If you are on  On Linux, you may first need to do: sudo groupadd docker && sudo usermod -aG docker $USERthis may require sudo (edit the promote_rc script to prefix all docker commands with sudo).

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 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, wait overnight for mirrors to sync, make the brew PR, then finalize the release.
   
   

...

*** this is a good time to call it a day...mirrors take overnight to sync the new release, and sometimes days for mavencentral ***

Don't forget to finish the remaining "Next steps" from promote_rc in the morning.

Final checks

(note: These steps are also covered by the "Next steps" from promote_rc)

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 has propagated to Maven Central.  Sometimes this may take a couple days, it seems?  Two ways to do 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)

...