Page History

...

```
git checkout ${RELEASE_BRANCH}
```
Run mvn version to set the proper rc number in all artifacts

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

Run Unit tests and ensure they succeed
1. ```
mvn test -DskipITs=true
```
Run Integration Tests and ensure they succeed
1. ```
mvn verify -DskipUTs=true
```
Commit and push this change to RELEASE branch

git commit -am “Bumping release candidate number ${RC_NUM}”

```
git push origin ${RELEASE_BRANCH}
```

Generate Source Release:

This will create the tarball under hudi/src_release directory

```
cd hudi/src_release
```

gpg --verify hudi-${RELEASE_VERSION}-rc${RC_NUM}.src.tgz.asc hudi-${RELEASE_VERSION}-rc${RC_NUM}.src.tgz

You should verify that the signature is good

tar -zxvf hudi-${RELEASE_VERSION}-rc${RC_NUM}.src.tgz && cd hudi-${RELEASE_VERSION}-rc${RC_NUM} && mvn clean package -DskipTests

If they pass, delete the repository we got from the tar-ball

cd ../ && rm -rf hudi-${RELEASE_VERSION}-rc${RC_NUM}

```
git checkout ${RELEASE_BRANCH}
```

cd scripts && ./release/create_source_release.sh

Verify Source release is signed and buildable

Create tag

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

if apache repo is origin.

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

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.

```
git checkout ${RELEASE_BRANCH}
```

This will deploy 2.11 artifacts to repository.apache.org

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

This will deploy 2.12 artifacts to repository.apache.org.
1. ```
./release/deploy_staging_jars.sh --scala_version=2.12 
```
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.
Close the staging repository on Apache Nexus. When prompted for a description, enter “Apache Hudi, version ${RELEASE_VERSION}, release candidate ${RC_NUM}”.

Stage source releases on dist.apache.org

If you have not already, check out the Hudi section of the dev repository on dist.apache.org via Subversion. In a fresh directory
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
```

Make a directory for the new release:

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

Copy Hudi source distributions, hashes, and GPG signature:

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

Add and commit all the files.

```
cd hudi 
```

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

```
svn commit
```

Verify that files are present

Run Verification Script to ensure the source release is sane

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

...

Maven artifacts deployed to the staging repository of repository.apache.org
Source distribution deployed to the dev repository of dist.apache.org and validated

Vote on the release candidate

...

Voting on dev@hudi group
Voting on general@incubator group
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.
...
From: Release Manager
To: dev@hudi.apache.org or general@incubator.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 "release-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
...
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.
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.
One more step is to deploy source code to release dist. https://dist.apache.org/repos/dist/release/hudi.
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.
Make a directory for the new release:
mkdir hudi/hudi-${RELEASE_VERSION}
Copy Hudi source distributions, hashes, and GPG signature:
mv <hudi-dir>/src_release/* hudi/hudi-${RELEASE_VERSION}
Add and commit all the files.
cd hudi
svn add hudi-${RELEASE_VERSION}
svn commit
Verify that files are present
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.
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'.
Finalize the Release in Jira by providing the release date.
Update DOAP file in the root of the project via sending a PR like this one.
...

Steps to cut doc version and update website.

Follow the instructions for cutting a doc for this new release.
Build the site locally and ensure the new doc version is available as intended.
Update site using instructions

Add download links for the new release to the website ??

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 after finalizing the release in accordance with the ASF release policy.

...

Space shortcuts

Page tree

Versions Compared

Old Version 4

New Version 5

Key

Vote on the release candidate

Steps to cut doc version and update website.

Add download links for the new release to the website ??

Promote the release