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}" 
```
  There will be some backup files created which needs to be removed. You could do "git clean -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.
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
```
    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}
7. 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}
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.
  3. ```
  git checkout ${RELEASE_BRANCH}
```
4. This will deploy scala 2.11 and spark 2 artifacts to repository.apache.orgcd scripts && ../scripts/release/deploy_staging_jars.sh --scala_version=2.11
5. This will deploy scala 2.12 and spark 2 artifacts to repository.apache.org.
  1. ```
  ./release/deploy_staging_jars.sh --scala_version=2.12 
```
  6. 2>&1 | tee -a "/tmp/${RELEASE_VERSION}-${RC_NUM}.deploy.log"
    1. make sure your IP is not changing while uploading, otherwise it creates a different staging repo
    2. Use a VPN if you can't prevent your IP from switching
    3. after uploading, inspect the log to make sure all maven tasks said "BUILD SUCCESS"
    This will deploy scala 2.12 and spark 3 artifacts to repository.apache.org.
    1. ./release/deploy_staging_jars.sh --scala_version=2.12 --spark_version=3
  7. 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
  8. 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.
  9. 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}”.
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
```

...

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.
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}
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}
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
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.
Create a new Github release, off the release version tag, you pushed before

...

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.

...

Space shortcuts

Page tree

Versions Compared

Old Version 46

New Version 47

Key