From f104b5512866b2292d893dafce4798ca883505d1 Mon Sep 17 00:00:00 2001 From: Andy Grove Date: Fri, 15 Nov 2024 14:34:01 -0700 Subject: [PATCH] Add hint for finding the GPG key to use when publishing to maven --- dev/release/README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/dev/release/README.md b/dev/release/README.md index fdf1065c0d..cd972aa1c3 100644 --- a/dev/release/README.md +++ b/dev/release/README.md @@ -172,6 +172,8 @@ Set up your development environment from here: https://infra.apache.org/publishi The script `publish-to-maven.sh` will publish the artifacts created by the `build-release-comet.sh` script. The artifacts will be signed using the gpg key of the release manager and uploaded to the maven staging repository. +Note that installed GPG keys can be listed with `gpg --list-keys`. The gpg key is a 40 character hex string. + Note: This script needs `xmllint` to be installed. On MacOS xmllint is available by default. On Ubuntu `apt-get install -y libxml2-utils`