Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. change the version from ${RELEASE_VERSION}-incubating-rc${RC_NUM} to ${RELEASE_VERSION}-incubating against release branch, use command `mvn versions:set -DnewVersion=${RELEASE_VERSION}-incubating`, e.g. change 0.5.1-incubating-rc1 to 0.5.1-incubating.
  2. 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. 
  3. One more step is to deploy source code to release dist. https://dist.apache.org/repos/dist/release/incubator/hudi.
    1. svn checkout https://dist.apache.org/repos/dist/release/incubator/hudi --depth=immediates, if you would not checkout, please try svn checkout https://dist.apache.org/repos/dist/release/incubator/hudi again.
    2. Make a directory for the new release:
      1.  mkdir hudi/hudi-${RELEASE_VERSION}-incubating
    3. Copy Hudi source distributions, hashes, and GPG signature: 
      1. mv <hudi-dir>/src_release/* hudi/hudi-${RELEASE_VERSION}-incubating
    4. Add and commit all the files. 
      1. cd hudi 
      2. svn add hudi-${RELEASE_VERSION}-incubating
      3. svn commit
    5. Verify that files are present
  4. 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.
  5. 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'.
  6. Finalize the Release in Jira by providing the release date. 


Steps to cut doc version and update website.

  1. Follow the  instructions for cutting a doc for this new release.
  2. Build the site locally  and ensure the new doc version is available as intended.
  3. 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 after finalizing the release in accordance with the ASF release policy.

...