THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- 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.
- git commit -am "[MINOR] Update release version to reflect published version ${RELEASE_VERSION}"
- 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.
- 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/${RELEASE_VERSION}
- Copy Hudi source distributions, hashes, and GPG signature:
- mv <hudi-dir>/src_release/* hudi/${RELEASE_VERSION}
- Add and commit all the files.
- cd hudi
- svn add ${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 candidateorgapachehudi-XXX
entry and clickRelease
. 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. - 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
...