yu199195 commented on a change in pull request #505:
URL:
https://github.com/apache/incubator-shenyu-website/pull/505#discussion_r832804619
##########
File path: community/5-release-guide.md
##########
@@ -64,337 +85,237 @@ Is this correct? (y/N) y
GnuPG needs to construct a user ID to identify your key.
-Real name: ${Input username}
-Email address: ${Input email}
-Comment: ${Input comment}
+Real name: （Set username）
+Email address: （Set email address）
+Comment: （Fill in the comments）
You selected this USER-ID:
- "${Inputed username} (${Inputed comment}) <${Inputed email}>"
+ "username (comments) <email>"
Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? O
-You need a Passphrase to protect your secret key. # Input passwords
+You need a Passphrase to protect your secret key. （Set password）
```
-**3. Check Generated Key**
+**2. Verify KEY**
+
+Follow [Operational GPG
Commands](https://www.gnupg.org/documentation/manuals/gnupg/Operational-GPG-Commands.html#Operational-GPG-Commands)
[2] instructions.
```shell
gpg --list-keys
```
-Execution Result:
+Output：
```shell
-pub 4096R/700E6065 2019-03-20
-uid ${Username} (${Comment}) <{Email}>
-sub 4096R/0B7EF5B2 2019-03-20
+pub rsa4096 2019-03-11 [SC]
+ 095E0D21BC28CFC7A8B8076DF7DF28D237A8048C
+uid username (comments) <email>
+sub rsa4096 2019-03-11 [E]
```
-700E6065 is public key ID.
+Public key is `095E0D21BC28CFC7A8B8076DF7DF28D237A8048C`.
-**4. Upload the Public Key to Key Server**
+**3. Upload public key**
-The command is as follows:
+Follow [Dirmngr
Options](https://www.gnupg.org/documentation/manuals/gnupg/Dirmngr-Options.html#Dirmngr-Options)
[3] instructions.
```shell
-gpg --keyserver hkp://pool.sks-keyservers.net --send-key 700E6065
+gpg --send-key 095E0D21BC28CFC7A8B8076DF7DF28D237A8048C
```
-`pool.sks-keyservers.net` is randomly chosen from [public key
server](https://sks-keyservers.net/status/).
-Each server will automatically synchronize with one another, so it would be
okay to choose any one.
-
-## Apache Maven Central Repository Release
+## Publish to Maven staging repo
**1. Set settings.xml**
-Add the following template to `~/.m2/settings.xml`, all the passwords need to
be filled in after encryption.
-For encryption settings, please see
[here](http://maven.apache.org/guides/mini/guide-encryption.html).
-
-```xml
-<settings>
- <servers>
- <server>
- <id>apache.snapshots.https</id>
- <username> <!-- APACHE LDAP username --> </username>
- <password> <!-- APACHE LDAP encrypted password --> </password>
- </server>
- <server>
- <id>apache.releases.https</id>
- <username> <!-- APACHE LDAP username --> </username>
- <password> <!-- APACHE LDAP encrypted password --> </password>
- </server>
- </servers>
-</settings>
-```
-
-**2. Update Release Notes**
+Follow [publishing maven
artifacts](https://infra.apache.org/publishing-maven-artifacts.html) [4]
instructions.
-Update the following file in master branch, and submit a PR to master branch:
-
-```
-https://github.com/apache/incubator-shenyu/blob/master/RELEASE-NOTES.md
-```
-
-**3. Create Release Branch**
+**2. Create and switch release branches**
Download and install [Git](https://git-scm.com/downloads)
-Suppose ShenYu source codes downloaded from github is under
`~/incubator-shenyu/` directory and the version to be released is
`${RELEASE.VERSION}`.
-Create `${RELEASE.VERSION}-release` branch, where all the following operations
are performed.
+Create and switch to `${PUBLISH.VERSION}-release`.
```shell
-# ${name} is the properly branch, e.g. master, main
-git clone --branch ${name} https://github.com/apache/incubator-shenyu.git
~/incubator-shenyu
+git clone https://github.com/apache/incubator-shenyu.git ~/incubator-shenyu
cd ~/incubator-shenyu/
-git pull
-git checkout -b ${RELEASE.VERSION}-release
-git push origin ${RELEASE.VERSION}-release
+git checkout -b ${PUBLISH.VERSION}-release
+git push origin ${PUBLISH.VERSION}-release
```
-**4. Pre-Release Check**
+**3. Dry Run**
Review comment:
add download maven
--
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]
