szehon-ho commented on code in PR #714: URL: https://github.com/apache/spark-website/pull/714#discussion_r4394414542
########## 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 see, hm. This came when i was trying to do the release, committer can only append keys to dev/<project>/KEYS, but not release/<project>/KEYS, the latter is automatically populated once release is done iiuc. the problem is, the VOTE email points to the release KEYS so nobody can validate until that happens and I get some -1 vote. just a one-time problem though. Not sure the solution -- 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]
