THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Use preparation_before_release.sh to setup GPG
- Script: preparation_before_release.sh
Usage ./hudi/scripts/release/preparation_before_release.sh
- Tasks included
- Help you create a new GPG key if you want.
- Configure git user.signingkey with chosen pubkey.
- Add chosen pubkey into dev KEYS and release KEYS
NOTES: Only PMC can write into release repo. - Start GPG agents.
...
Here, the key ID is the 8-digit hex string in the pub line: 845E6689 or more than 8-digit hex string like 623E08E06DB376684FB9599A3F5953147903948A.
Now, add your Apache GPG key to the Hudi’s KEYS file both in dev and release repositories at dist.apache.org. Follow the instructions listed at the top of these files. (Note: Only PMC members have write access to the release repository. If you end up getting 403 errors ask on the mailing list for assistance.)
...
- Release Manager’s GPG key is published to dist.apache.org
- Release Manager’s GPG key is configured in git configuration
- Release Manager has org.apache.hudi listed under Staging Profiles in Nexus
- Release Manager’s Nexus User Token is configured in settings.xml
- JIRA release item for the subsequent release has been created
- All test failures from branch verification have associated JIRA issues
- There are no release blocking JIRA issues
- Release branch has been created
- Release Notes have been audited and added to RELEASE_NOTES.md
Build a release candidate
...