You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hugegraph.apache.org by ji...@apache.org on 2023/01/16 19:44:38 UTC

[incubator-hugegraph-doc] branch imbajin-patch-1 created (now 2bf53ce7)

This is an automated email from the ASF dual-hosted git repository.

jin pushed a change to branch imbajin-patch-1
in repository https://gitbox.apache.org/repos/asf/incubator-hugegraph-doc.git


      at 2bf53ce7 Update validate-release.md

This branch includes the following new commits:

     new 2bf53ce7 Update validate-release.md

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.



[incubator-hugegraph-doc] 01/01: Update validate-release.md

Posted by ji...@apache.org.
This is an automated email from the ASF dual-hosted git repository.

jin pushed a commit to branch imbajin-patch-1
in repository https://gitbox.apache.org/repos/asf/incubator-hugegraph-doc.git

commit 2bf53ce7dcf967f82b55eca4af08a8ba4362e1f7
Author: imbajin <ji...@apache.org>
AuthorDate: Tue Jan 17 03:44:34 2023 +0800

    Update validate-release.md
---
 .../en/docs/contribution-guidelines/validate-release.md    | 14 +++++++++++---
 1 file changed, 11 insertions(+), 3 deletions(-)

diff --git a/content/en/docs/contribution-guidelines/validate-release.md b/content/en/docs/contribution-guidelines/validate-release.md
index 84dab47b..5fa8e287 100644
--- a/content/en/docs/contribution-guidelines/validate-release.md
+++ b/content/en/docs/contribution-guidelines/validate-release.md
@@ -55,19 +55,27 @@ gpg --import KEYS
 
 # After importing, you can see the following output, which means that 3 user public keys have been imported
 gpg: /home/ubuntu/.gnupg/trustdb.gpg: trustdb created
-gpg: key B78B058CC255F6DC: public key "Imba Jin (apache mail) <ji...@apache.org>" imported
+gpg: key BA7E78F8A81A885E: public key "imbajin (apache mail) <ji...@apache.org>" imported
 gpg: key 818108E7924549CC: public key "vaughn <va...@apache.org>" imported
 gpg: key 28DCAED849C4180E: public key "coderzc (CODE SIGNING KEY) <zh...@apache.org>" imported
 gpg: Total number processed: 3
 gpg:               imported: 3
 
-# 2. Trust release users (here you need to trust 3 users, perform the same operation for Imba Jin, vaughn, coderzc in turn)
-gpg --edit-key Imba Jin # Take the first one as an example, enter the interactive mode
+# 2. Trust release users (you need trust x username mentioned in voting mail, if more than 1 user, just repeat the steps in turn or use script)
+gpg --edit-key $USER # input the username, enter the interactive mode
 gpg> trust
 ...output options..
 Your decision? 5 #select five
 Do you really want to set this key to ultimate trust? (y/N) y #slect y, then q quits trusting the next user
 
+You could also use the command to trust one user in non-interactive mode:
+echo -e "5\ny\n" | gpg --batch --command-fd 0 --edit-key $USER trust
+
+Or use the script to auto import all public keys (be carefully):
+for key in $(gpg --no-tty --list-keys --with-colons | awk -F: '/^pub/ {print $5}'); do
+  echo -e "5\ny\n" | gpg --batch --command-fd 0 --edit-key "$key" trust
+done
+
 
 # 3. Check the signature (make sure there is no Warning output, every source/binary file prompts Good Signature)
 #Single file verification