Skip to content

Commit bfd7054

Browse files
authored
Add hint for finding the GPG key to use when publishing to maven (#1093)
1 parent 406ffef commit bfd7054

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

dev/release/README.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -172,6 +172,8 @@ Set up your development environment from here: https://infra.apache.org/publishi
172172
The script `publish-to-maven.sh` will publish the artifacts created by the `build-release-comet.sh` script.
173173
The artifacts will be signed using the gpg key of the release manager and uploaded to the maven staging repository.
174174

175+
Note that installed GPG keys can be listed with `gpg --list-keys`. The gpg key is a 40 character hex string.
176+
175177
Note: This script needs `xmllint` to be installed. On MacOS xmllint is available by default.
176178

177179
On Ubuntu `apt-get install -y libxml2-utils`

0 commit comments

Comments
 (0)