pan3793 commented on code in PR #714: URL: https://github.com/apache/spark-website/pull/714#discussion_r4384644226
########## release-process.md: ########## @@ -139,15 +139,21 @@ To get the code signing key (a.k.a ASCII-armored public key), run the command: $ gpg --export --armor 3FF6D044 ``` -And then append the generated key to the KEYS file by: +And then append the generated key to the staging KEYS file by: Review Comment: I remember a few years ago (I cannot find the exact email, it happened in the incubating list, many incubating projects were coached there on how to perform an Apache release), ASF asked us to always use `.../release/<project>/KEYS` in the voting email instead of `.../dev/<project>/KEYS`. So we don't need to maintain the `.../dev/spark/KEYS` actually, and the command can be updated in-place to point to the `.../release/<project>/KEYS` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
