...
- Create a GPG key
- gpg --full-generate-key
- Determine your Apache GPG Key and Key ID, as follows:
- gpg --list-keys
- This will list your GPG keys. One of these should reflect your Apache account, for example:
- --------------------------------------------------
- pub 2048R/935D191 2019-08-29
- uid Anonymous Anonymous <anonymous@apache.org>
- sub 2048R/CD4C59FD 2019-08-29
or
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.)
- Configure git to use this key when signing code by giving it your key ID, as follows:
- git config --global user.signingkey CD4C59FD, or git config --global user.signingkey 623E08E06DB376684FB9599A3F5953147903948A
- You may drop the --global option if you’d prefer to use this key for the current repository only.
- Start GPG agent in order to unlock your GPG key
- eval $(gpg-agent --daemon --no-grab --write-env-file $HOME/.gpg-agent-info)
- export GPG_TTY=$(tty)
- export GPG_AGENT_INFO
...
In order to make yourself have the right permission to stage java artifacts in Apache Nexus staging repository, please submit your GPG public key into MIT PGP Public Key Server. If you have problem in submit your GPG key to the key server in browse, please try run
gpg --keyserver hkp://pool.sks-keyservers.net --send-keys ${PUBLIC_KEY} and verify via gpg --keyserver hkp://pool.sks-keyservers.net --recv-keys ${PUBLIC_KEY},
also send public key to ubuntu server via gpg --keyserver hkp://keyserver.ubuntu.com --send-keys ${PUBLIC_KEY}, and verify via gpg --keyserver hkp://keyserver.ubuntu.com --recv-keys ${PUBLIC_KEY},
would also refer to stackoverflow.
Create a new version in JIRA
...