Page History

Table of Contents

Introduction

This release process document is based on Apache Beam Release Guide and Apache Flink Release Guide

...

1. Community agrees to release
2. Community selects a Release Manager

Prepare for the release 

As a release manager, you should create a private Slack channel, named `hudi-<version>_release_work` (e.g. hudi-0_12_0_release_work) in Apache Hudi Slack for coordination. Invite all committers to the channel.

Before your first release, you should perform one-time configuration steps. This will set up your security keys for signing the release and access to various release repositories.

...

NOTE: If you are using GitHub two-factor authentication and haven’t configure HTTPS access, please follow the guide to configure command line access.

One-time

...

Setup Instructions

...

GPG Key

You need to have a GPG key to sign the release artifacts. Please be aware of the ASF-wide release signing guidelines. If you don’t have a GPG key associated with your Apache account, please create one according to the guidelines.follow the section below.

For Linux users

There are 2 ways to configure your GPG key for release, either using release automation script(which is recommended), or running all commands manually. If using Mac, please see below to handle known issues.

Use preparation_before_release.sh to setup GPG

• Script: preparation_before_release.sh

• Usage  ./hudi/scripts/release/preparation_before_release.sh

• Tasks included
1. Help you create a new GPG key if you want.
2. Configure git user.signingkey with chosen pubkey.
3. Add chosen pubkey into dev KEYS and release KEYS
   NOTES: Only PMC can write into release repo.
4. Start GPG agents.

...

Here, the key ID is the 8-digit hex string in the pub line: 845E6689 or more than 8-digit hex string like 623E08E06DB376684FB9599A3F5953147903948A.
Now, add your Apache GPG key to the Hudi’s  KEYS file both in dev and release repositories at dist.apache.org. Follow the instructions listed at the top of these files. (Note: Only PMC members have write access to the release repository. If you end up getting 403 errors ask on the mailing list for assistance.)

• Configure git to use this key when signing code by giving it your key ID, as follows:

• git config --global user.signingkey CD4C59FD, or git config --global user.signingkey 623E08E06DB376684FB9599A3F5953147903948A

• You may drop the --global option if you’d prefer to use this key for the current repository only.
• Start GPG agent in order to unlock your GPG key

• eval $(gpg-agent --daemon --no-grab --write-env-file $HOME/.gpg-agent-info)

• export GPG_TTY=$(tty)

• export GPG_AGENT_INFO

If using Mac you might encounter these issues with the not time setup

For Mac users

• apt-get is not available . So install gpg using  https://gpgtools.org/ 
• Create gpg key with your apache emailId and publish to key server (refer to the section "Submit your GPG public key into MIT PGP Public Key Server"  below)
• The KEYS file is in https://dist.apache.org/repos/dist/

...

• • To

...

• • checkout you

...

• • need subversion

...

• • . If subversion is not available in Mac you might have to first install it using `brew install subversion`.

...

Access to Apache Nexus repository

...

<settings>
   <servers>
     <server>
       <id>apache.releases.https</id>
       <username>TOKEN_NAME</username>
       <password>TOKEN_PASSWORD</password>
     </server>
     <server>
       <id>apache.snapshots.https</id>
       <username>TOKEN_NAME</username>
       <password>TOKEN_PASSWORD</password>
     </server>
   </servers>
 </settings>

Submit your GPG public key into MIT PGP Public Key Server

In order to make yourself have the right permission to stage java artifacts in Apache Nexus staging repository, please submit your GPG public key into MIT PGP Public Key Server. If you have problem in submit your GPG

Also send public key to the key server in browse, please try runubuntu server via



gpg --keyserver hkp://poolkeyserver.sks-keyserversubuntu.netcom --send-keys ${PUBLIC_KEY} and# verifysend viapublic gpgkey --keyserver hkp://pool.sks-keyservers.net --recv-keys ${PUBLIC_KEY}

...

gpg --keyserver hkp://keyserver.ubuntu.com --send-keys ${PUBLIC_KEY} # send public key to ubuntu to ubuntu server
gpg --keyserver hkp://keyserver.ubuntu.com --recv-keys ${PUBLIC_KEY} # verify 

...

• Create a branch in your repo (<user>/hudi). 
• cherry pick commits from master that needs to be part of this release. (git cherry-pick commit-hash). You need to manually resolve the conflicts. For eg, a file might have been moved to a diff class in master where as in your release branch, it could be in older place. You need to take a call where to place it. Similar things like file addition, file deletion, etc. 
• Update the release version by running "mvn versions:set -DnewVersion=${RELEASE}-rc${RC_NUM}", with "RELEASE" as the version and "RC_NUM" as the RC number.  Make sure the version changes are intended.  Then git commit the changes.
• Ensure both compilation Ensure both compilation and tests are good. 
• I assume you will have apache/hudi as upstream. If not add it as upstream
• Once the branch is ready with all commits, go ahead and push your branch to upstream. 
• Go to apache/hudi repo locally and pull this branch. Here after you can work on this branch and push to origin when need be. 
• Do not forget to set the env variables from above section. 

Verify that a Release Build Works 

Run "mvn -Prelease clean install to " to ensure that the build processes are in good shape. // You need to execute this command once you have the release branch in apache/hudi

Checklist to proceed to the next step

Good to run this for all profiles

mvn -Prelease clean install
mvn -Prelease clean install -Dscala-2.12
mvn -Prelease clean install -Dspark3

Checklist to proceed to the next step

• Release Manager’s Release Manager’s GPG key is published to dist.apache.org
• Release Manager’s GPG key is configured in git configuration
• Release Manager has org.apache.hudi listed under Staging Profiles in Nexus
• Release Manager’s Nexus User Token is configured in settings.xml
• JIRA release item for the subsequent release has been created
• All test failures from branch verification have associated JIRA issues
• There are no release blocking JIRA issues
• Release branch has been created
• Release Notes  have been audited and added to RELEASE_NOTES.md

Build a release candidate

...

Set up a few environment variables to simplify Maven commands that follow. This identifies the release candidate being built. Start with RC_NUM equal to 1 and increment it for each candidate. 

1. 1. git checkout ${RELEASE_BRANCH}

   2. Run mvn version to set the proper rc number in all artifacts

      1. mvn versions:set -DnewVersion=${RELEASE_VERSION}-rc${RC_NUM}

   3. Run Unit tests  and ensure they succeed

      1. mvn test -DskipITs=true

   4. Run Integration Tests and ensure they succeed

      1. mvn verify -DskipUTs=true

   5. Commit and push this change to RELEASE branch

      1. git commit -am "Bumping release candidate number ${RC_NUM}" 

         There will be some backup files created which needs to be removed. You could do "git clean -

fdx

2. 1. 1. fd" before doing the commit.

      2. git push origin ${RELEASE_BRANCH}
         

         If you already have a remote tag with same name as your branch, you can try below command.

         git push origin refs/heads/${RELEASE_BRANCH}

         "refs/heads/" refers to a branch.

         "refs/tags/" refers to tag.

   2. Generate Source Release: This will create the tarball under hudi/src_release directory

      1. git checkout ${RELEASE_BRANCH}

      2. cd scripts && ./release/create_source_release.sh
         

         If you have multiple gpg keys(gpg --list-keys), then the signing command will take in the first key most likely. You will release this when it asks for a passphrase in a pop up. When asked for passphrase, ensure the intended key is the one asked for. 

         Command used in script:

         gpg --armor --detach-sig ${RELEASE_DIR}/hudi-${RELEASE_VERSION}.src.tgz

         To use a specific key: update as follows: // replace FINGERPRINT

         gpg --local-user [FINGERPRINT] --armor --detach-sig ${RELEASE_DIR}/hudi-${RELEASE_VERSION}.src.tgz

      3. Verify Source release is signed and buildable
         1. cd hudi/src_release
         2. gpg --verify hudi-${RELEASE_VERSION}-rc${RC_NUM}.src.tgz.asc hudi-${RELEASE_VERSION}-rc${RC_NUM}.src.tgz
         3. tar -zxvf hudi-${RELEASE_VERSION}-rc${RC_NUM}.src.tgz && cd hudi-${RELEASE_VERSION}-rc${RC_NUM} && mvn clean package -DskipTests -Pintegration-tests
         4. If they pass, delete the repository we got from the tar-ball
            1. cd ../ && rm -rf hudi-${RELEASE_VERSION}-rc${RC_NUM}
   3. Create tag 

      1. git tag -s release-${RELEASE_VERSION}-rc${RC_NUM} -m "${RELEASE_VERSION}"
         

         If you run into some issues, and if want to re-run the same candidate again from start, ensure you delete existing tags before retrying again.

         // to remove local

         git tag -d release-${RELEASE_VERSION}-rc${RC_NUM}

         // to remove remote
         git push --delete origin release-${RELEASE_VERSION}-rc${RC_NUM}

      2. if apache repo is origin.

         1. git push origin release-${RELEASE_VERSION}-rc${RC_NUM} 

            If a branch with the same name already exists in origin, this command might fail as below.

            error: src refspec release-0.5.3 matches more than one

            error: failed to push some refs to 'https://github.com/apache/hudi.git'

            In such a case, try below command

            git push origin refs/tags/release-${RELEASE_VERSION}-rc${RC_NUM}

3. Deploy maven artifacts and verify
   1. This will deploy jar artifacts to the Apache Nexus Repository, which is the staging area for deploying jars to Maven Central. 
   2. Review all staged artifacts (https://repository.apache.org/). They should contain all relevant parts for each module, including pom.xml, jar, test jar, source, test source, javadoc, etc. Carefully review any new artifacts.

1. git checkout ${RELEASE_BRANCH}

2. This will deploy 2.11 artifacts to repository.apache.org

   1. cd scripts && ./release/deploy_staging_jars.sh --scala_version=2.11

3. This will deploy 2.12 artifacts to repository.apache.org.

   1. ./release/deploy_staging_jars.sh --scala_version=2.12 

4. Review all staged artifacts to ensure it contains both 2.11 and 2.12 artifacts, mainly hudi-spark-bundle-2.11/2.12, hudi-spark-2.11/2.12, hudi-utilities-bundle_2.11/2.12 and hudi-utilities_2.11/2.12.
5. Once you have ensured everything is good and validation of step 7 succeeds, you can close the staging repo. Closing is kind of commit. Until you close, you can re-run deploying to staging multiple times. But once closed, it will create a new staging repo. So, once everything is good, close the staging repository on Apache Nexus. When prompted for a description, enter “Apache Hudi, version ${RELEASE_VERSION}, release candidate ${RC_NUM}”.
4. Stage source releases on dist.apache.org
1. If you have not already, check out the Hudi section of the dev repository on dist.apache.org via Subversion. In a fresh directory
2. if you would not checkout, please try svn checkout https://dist.apache.org/repos/dist/dev/hudi again.

   1. svn checkout https://dist.apache.org/repos/dist/dev/hudi --depth=immediates

3. Make a directory for the new release:

   1.  mkdir hudi/hudi-${RELEASE_VERSION}-rc${RC_NUM}

4. Copy Hudi source distributions, hashes, and GPG signature: 

   1. mv <hudi-dir>/src_release/* hudi/hudi-${RELEASE_VERSION}-rc${RC_NUM}

5. Add and commit all the files. 

   1. cd hudi 

   2. svn add hudi-${RELEASE_VERSION}-rc${RC_NUM}

   3. svn commit

6. Verify that files are present
7. Run Verification Script to ensure the source release is sane

   1. cd scripts && ./release/validate_staged_release.sh --release=${RELEASE_VERSION} --rc_num=${RC_NUM} --verbose

Checklist to proceed to the next step

1. Maven artifacts deployed to the staging repository of repository.apache.org

2. Source distribution deployed to the dev repository of dist.apache.org and validated

Vote on the release candidate 

Once you have built and individually reviewed the release candidate, please share it for the community-wide(dev@hudi ) review. Please review foundation-wide voting guidelines for more information.

Start the review-and-vote thread on the dev@ mailing list. Here’s an email template; please adjust as you see fit.

...

From: Release Manager

To: dev@hudi.apache.org 

Subject: [VOTE] Release 1.2.3, release candidate #3

Hi everyone,

Please review and vote on the release candidate #3 for the version 1.2.3, as follows:

[ ] +1, Approve the release

[ ] -1, Do not approve the release (please provide specific comments)

The complete staging area is available for your review, which includes:

* JIRA release notes [1],

* the official Apache source release and binary convenience releases to be deployed to dist.apache.org [2], which are signed with the key with fingerprint FFFFFFFF [3],

* all artifacts to be deployed to the Maven Central Repository [4],

* source code tag "1.2.3-rc3" [5],

The vote will be open for at least 72 hours. It is adopted by majority approval, with at least 3 PMC affirmative votes.

Thanks,

Release Manager

[1] link

[2] link

[3] https://dist.apache.org/repos/dist/release/hudi/KEYS

[4] link

[5] link

[6] link

1. 1. Stage source releases on dist.apache.org
      1. If you have not already, check out the Hudi section of the dev repository on dist.apache.org via Subversion. In a fresh directory
      2. if you would not checkout, please try svn checkout https://dist.apache.org/repos/dist/dev/hudi again.

         1. svn checkout https://dist.apache.org/repos/dist/dev/hudi --depth=immediates

      3. Make a directory for the new release:

         1.  mkdir hudi/hudi-${RELEASE_VERSION}-rc${RC_NUM}

      4. Copy Hudi source distributions, hashes, and GPG signature: 

         1. mv <hudi-dir>/src_release/* hudi/hudi-${RELEASE_VERSION}-rc${RC_NUM}

      5. Add and commit all the files. 

         1. cd hudi 

         2. svn add hudi-${RELEASE_VERSION}-rc${RC_NUM}

         3. svn commit

      6. Verify that files are present
      7. Run Verification Script to ensure the source release is sane

         1. For RC: cd scripts && ./release/validate_staged_release.sh --release=${RELEASE_VERSION} --rc_num=${RC_NUM} --verbose

         2. For finalized release in dev: cd scripts && ./release/validate_staged_release.sh --release=${RELEASE_VERSION} --verbose
   2. Deploy maven artifacts and verify
      1. This will deploy jar artifacts to the Apache Nexus Repository, which is the staging area for deploying jars to Maven Central. 
      2. Review all staged artifacts (https://repository.apache.org/). They should contain all relevant parts for each module, including pom.xml, jar, test jar, source, test source, javadoc, etc. Carefully review any new artifacts.

      3. git checkout ${RELEASE_BRANCH}
         

      4. ./scripts/release/deploy_staging_jars.sh 2>&1 | tee -a "/tmp/${RELEASE_VERSION}-${RC_NUM}.deploy.log"
         1. when prompted for the passphrase, if you have multiple gpg keys in your keyring, make sure that you enter the right passphase corresponding to the same key (FINGERPRINT) as used while generating source release in step f.ii.

            1. If the prompt is not for the same key (by default the maven-gpg-plugin will pick up the first key in your keyring so that could be different), then add the following option to your ~/.gnupg/gpg.conf file

               Code Block
               default-key <FINGERPRINT_OF_KEY_USED_FOR_SOURCE_RELEASE>

               
               

         2. make sure your IP is not changing while uploading, otherwise it creates a different staging repo
         3. Use a VPN if you can't prevent your IP from switching
         4. after uploading, inspect the log to make sure all maven tasks said "BUILD SUCCESS"
      5. Review all staged artifacts by logging into Apache Nexus and clicking on "Staging Repositories" link on left pane. Then find a "open" entry for apachehudi
      6. Ensure it contains all 3 (2.11, 2.12 with spark2 and 2.12 with spark3) artifacts, mainly hudi-spark-bundle-2.11/2.12, hudi-spark3-bundle-2.12, hudi-spark-2.11/2.12, hudi-spark2-2.11/2.12, hudi-spark3-2.12, hudi-utilities-bundle_2.11/2.12 and hudi-utilities_2.11/2.12.
         1. With 0.10.1, we had 4 bundles. spark2 with scala11, spark2 with scala12, spark3.0.x bundles and spark3.1.x bundles. Ensure each spark bundle reflects the version correctly. hudi-spark3.1.2-bundle_2.12-0.10.1.jar and hudi-spark3.0.3-bundle_2.12-0.10.1.jar are the respective bundle names for spark3 bundles. 
      7. Once you have ensured everything is good and validation of step 7 succeeds, you can close the staging repo. Until you close, you can re-run deploying to staging multiple times. But once closed, it will create a new staging repo. So ensure you close this, so that the next RC (if need be) is on a new repo. So, once everything is good, close the staging repository on Apache Nexus. When prompted for a description, enter “Apache Hudi, version ${RELEASE_VERSION}, release candidate ${RC_NUM}”.
      8. After closing, run the script to validate the staged bundles again:

         1. ./scripts/release/validate_staged_bundles.sh orgapachehudi-<stage_repo_number> ${RELEASE_VERSION}-rc${RC_NUM} 2>&1 | tee -a /tmp/validate_staged_bundles_output.txt

Checklist to proceed to the next step

1. Maven artifacts deployed to the staging repository of repository.apache.org

2. Source distribution deployed to the dev repository of dist.apache.org and validated

Vote on the release candidate 

Once you have built and individually reviewed the release candidate, please share it for the community-wide(dev@hudi ) review. Please review foundation-wide voting guidelines for more information.

Start the review-and-vote thread on the dev@ mailing list.

If there are any issues found in the release candidate, reply on the vote thread to cancel the vote, and there’s no need to wait 72 hours if any issues found. Proceed to the Fix Issues step below and address the problem. However, some issues don’t require cancellation. For example, if an issue is found in the website, just correct it on the spot and the vote can continue as-is.

If there are no issues, reply on the vote thread to close the voting. Then, tally the votes in a separate email. Here’s an email template; please adjust as you see fit.

Please look at previous examples in previous releases. For example : Please see examples here : voting in dev ,  voting in general and result of voting

Checklist to proceed to the finalization step

1. Community votes to release the proposed candidate, with at least three approving PMC votes

Fix any issues

Any issues identified during the community review and vote should be fixed in this step.

Code changes should be proposed as standard pull requests to the master branch and reviewed using the normal contributing process. Then, relevant changes should be cherry-picked into the release branch. The cherry-pick commits should then be proposed as the pull requests against the release branch, again reviewed and merged using the normal contributing process.

Once all issues have been resolved, you should go back and build a new release candidate with these changes.

Checklist to proceed to the next step

1. Issues identified during vote have been resolved, with fixes committed to the release branch.

Finalize the release

Once the release candidate has been reviewed and approved by the community, the release should be finalized. This involves the final deployment of the release candidate to the release repositories, merging of the website changes, etc.

Current follow the below steps to finalize the release.

1. change the version from ${RELEASE_VERSION}-rc${RC_NUM} to ${RELEASE_VERSION} against release branch, use command `mvn versions:set -DnewVersion=${RELEASE_VERSION}`, e.g. change 0.5.1-rc1 to 0.5.1.
2. Commit and push the version change to release branch.
   1. git commit -am '[MINOR] Update release version to reflect published version  ${RELEASE_VERSION}'
   2. git push origin release-${RELEASE_VERSION}
3. Repeat the steps from Generate Source Release(f) to Stage source releases on dist.apache.org(i). Note that make sure remove the -rc${RC_NUM} suffix when repeat the above steps. and please also verify the steps.  Ensure git tag is also done without  -rc${RC_NUM}
4. One more step is to deploy source code to release dist. https://dist.apache.org/repos/dist/release/hudi. Only PMC will have access to this repo. So, if you are not a PMC, do get help from somone who is. 
   1. svn checkout https://dist.apache.org/repos/dist/release/hudi --depth=immediates, if you would not checkout, please try svn checkout https://dist.apache.org/repos/dist/release/hudi again.
   2. Make a directory for the new release:
      1.  mkdir hudi/hudi-${RELEASE_VERSION}
   3. Copy Hudi source distributions, hashes, and GPG signature: 
      1. mv <hudi-dir>/src_release/* hudi/${RELEASE_VERSION}
   4. Add and commit all the files. 
      1. cd hudi 
      2. svn add hudi-${RELEASE_VERSION}
      3. svn commit
   5. Verify that files are present
5. Use the Apache Nexus repository to release the staged binary artifacts to the Maven Central repository. In the Staging Repositories section, find the relevant release candidate orgapachehudi-XXX entry and click Release. Drop all other release candidates that are not being released.
6. In Jira, go to Releases → <Release Version> and ensure that all Jiras for the release are 'Closed' state, if not transition all 'Resolved' jiras to 'Closed'.
7. Finalize the Release in Jira by providing the release date. 
8. Update DOAP file in the root of the project via sending a PR like this one.

Steps to cut doc version and update website.

If there are any issues found in the release candidate, reply on the vote thread to cancel the vote, and there’s no need to wait 72 hours if any issues found. Proceed to the Fix Issues step below and address the problem. However, some issues don’t require cancellation. For example, if an issue is found in the website, just correct it on the spot and the vote can continue as-is.

If there are no issues, reply on the vote thread to close the voting. Then, tally the votes in a separate email. Here’s an email template; please adjust as you see fit.

Please look at previous examples in previous releases. For example : Please see examples here : voting in dev ,  voting in general and result of voting

Checklist to proceed to the finalization step

1. Community votes to release the proposed candidate, with at least three approving PMC votes

Fix any issues

Any issues identified during the community review and vote should be fixed in this step.

Code changes should be proposed as standard pull requests to the master branch and reviewed using the normal contributing process. Then, relevant changes should be cherry-picked into the release branch. The cherry-pick commits should then be proposed as the pull requests against the release branch, again reviewed and merged using the normal contributing process.

Once all issues have been resolved, you should go back and build a new release candidate with these changes.

Checklist to proceed to the next step

1. Issues identified during vote have been resolved, with fixes committed to the release branch.

Finalize the release

Once the release candidate has been reviewed and approved by the community, the release should be finalized. This involves the final deployment of the release candidate to the release repositories, merging of the website changes, etc.

Current follow the below steps to finalize the release.

1. change the version from ${RELEASE_VERSION}-rc${RC_NUM} to ${RELEASE_VERSION} against release branch, use command `mvn versions:set -DnewVersion=${RELEASE_VERSION}`, e.g. change 0.5.1-rc1 to 0.5.1.
2. Commit and push the version change to release branch.
   1. git commit -am "[MINOR] Update release version to reflect published version  ${RELEASE_VERSION}"
   2. git push origin release-${RELEASE_VERSION}
3. Repeat the steps from Generate Source Release(f) to Stage source releases on dist.apache.org(i). Including staging jars with the release version and uploading source release. Note that make sure remove the -rc${RC_NUM} suffix when repeat the above steps. and please also verify the steps.  Ensure git tag is also done without  -rc${RC_NUM}
4. One more step is to deploy source code to release dist. https://dist.apache.org/repos/dist/release/hudi. Only PMC will have access to this repo. So, if you are not a PMC, do get help from somone who is. 
   1. svn checkout https://dist.apache.org/repos/dist/release/hudi --depth=immediates, if you would not checkout, please try svn checkout https://dist.apache.org/repos/dist/release/hudi again.
   2. Make a directory for the new release:
      1.  mkdir hudi/${RELEASE_VERSION}
   3. Copy Hudi source distributions, hashes, and GPG signature: 
      1. mv <hudi-dir>/src_release/* hudi/${RELEASE_VERSION}
   4. Add and commit all the files. 
      1. cd hudi 
      2. svn add ${RELEASE_VERSION}
      3. svn commit
   5. Verify that files are present
5. Use the Apache Nexus repository to release the staged binary artifacts to the Maven Central repository. In the Staging Repositories section, find the relevant release candidate orgapachehudi-XXX entry and click Release. Drop all other release candidates that are not being released.  It can take up to 24 hours for the new release to show up in Maven Central repository. 
6. In Jira, go to Releases → <Release Version> and ensure that all Jiras for the release are 'Closed' state, if not transition all 'Resolved' jiras to 'Closed'.
7. Finalize the Release in Jira by providing the release date. 
8. Update DOAP file in the root of the project via sending a PR like this one.
9. Create a new Github release, off the release version tag, you pushed before

Steps to cut doc version and update website.

1. Follow the instructions for cutting a doc for this new release.
   1. For a minor release, make sure any docs updates regarding the new features for the next major release, not in the minor release, are excluded.  This involves reverting the changes or manually removing the relevant docs in a separate branch.
2. Build the site locally  and ensure the new doc version is available as intended.
3. Update site using instructions
4. There are few adhoc fixes that needs to be taken care apart from above steps. Adding examples of commits from 0.10.1 that you can follow. 
   1. https://github.com/apache/hudi/pull/4703/commits/1e7c9af976b075c9ed5a780da1cdb57f019a41d3
   2. https://github.com/apache/hudi/pull/4703/commits/b474ec266fe2243f8146ba7a112045bbc8b0ddc8
   3. https://github.com/apache/hudi/commit/549fa7a51b30b162dcd6fc70b42cf1779de1900b
   4. https://github.com/apache/hudi/commit/de3405855c23aeb449113de197591c186396a4c2
5. Follow the  instructions for cutting a doc for this new release.
6. Build the site locally  and ensure the new doc version is available as intended.
7. Update site using instructions

Promote the release

Once the release has been finalized, the last step of the process is to promote the release within the project and beyond. Please wait for 24h 1h after finalizing the release in accordance with the ASF release policy.

...

...