Page History

...

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}”

2. git push origin ${RELEASE_BRANCH}

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

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

1. git checkout ${RELEASE_BRANCH}

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

3. Verify Source release is signed and buildable
7. Create tag 

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

   2. if apache repo is origin.

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

8. 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. Close the staging repository on Apache Nexus. When prompted for a description, enter “Apache Hudi, version ${RELEASE_VERSION}, release candidate ${RC_NUM}”.
9. 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

...