This is an automated email from the ASF dual-hosted git repository.
huxing pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/incubator-dubbo-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new d9f962b Polish apache release doc.
d9f962b is described below
commit d9f962be8bcbc205b51e462c0da1cb9c058f2341
Author: Huxing Zhang <[email protected]>
AuthorDate: Wed Jan 16 21:59:04 2019 +0800
Polish apache release doc.
---
blog/en-us/prepare-an-apache-release.md | 24 +++++++++++++++---------
1 file changed, 15 insertions(+), 9 deletions(-)
diff --git a/blog/en-us/prepare-an-apache-release.md
b/blog/en-us/prepare-an-apache-release.md
index 4669958..692f286 100644
--- a/blog/en-us/prepare-an-apache-release.md
+++ b/blog/en-us/prepare-an-apache-release.md
@@ -145,9 +145,10 @@ modifications and taggings related to ${release_version}
Release Candidates are
```shell
$ mvn clean install -Papache-release
$ mvn deploy
- # push the snapshot package to the maven central repository,in staging state
```
+ This push the snapshot package to the maven central repository.
+
3. Release with maven-release-plugin
- verify with dryRun
@@ -161,16 +162,21 @@ modifications and taggings related to ${release_version}
Release Candidates are
```shell
$ mvn release:clean
$ mvn release:prepare -Papache-release -Darguments="-DskipTests"
-DautoVersionSubmodules=true -Dusername=YOUR GITHUB ID
- # After running：1. Generate source.zip; 2. Tag and push to github
repository; 3. The branch version is upgraded to ${release_version}-SNAPSHOT
automatically and the modifications are pushed to the github repository
```
+ After executing the above commands, you will find that:
+ 1. Generate source.zip
+ 2. Tag and push to github repository
+ 3. The branch version is upgraded to ${release_version}-SNAPSHOT
automatically and the modifications are pushed to the github repository
+
- Run release:perform, make an offical release
```shell
$ mvn -Prelease release:perform -Darguments="-DskipTests"
-DautoVersionSubmodules=true -Dusername=YOUR GITHUB ID
- # All artifacts are released to configured remote maven central
repository, in staging state
```
+ All artifacts are released to configured remote maven central repository,
in staging state
+
## Prepare Apache Release
1. Prepare the svn local environment (Apache hosting the release content of
project by svn)
@@ -183,14 +189,14 @@ modifications and taggings related to ${release_version}
Release Candidates are
~/apache/incubator/dubbo
```
-3. The current release version is ${release_version},new directory
+3. The current release version is ${release_version}, new directory
```shell
$ cd ~/apache/incubator/dubbo # dubbo svn root directory
$ mkdir ${release_version}
```
-4. Add public key to
[KEYS](https://dist.apache.org/repos/dist/dev/incubator/dubbo/KEYS) file.KEYS
is mainly used to allow people who participate in the voting to be imported
locally to verify the correctness of the sign.
+4. Add public key to
[KEYS](https://dist.apache.org/repos/dist/dev/incubator/dubbo/KEYS) file. KEYS
is mainly used to allow people who participate in the voting to be imported
locally to verify the correctness of the sign.
5. Copy the source.zip package from the Dubbo root directory to the svn local
repository dubbo/${release_version}
@@ -223,7 +229,7 @@ The verification link includes but is not limited to the
following contents and
1. Check signatures and hashes are good
* sha512
-```sh
+ ```sh
$ shasum -c
apache-dubbo-incubating-${release_version}-source-release.zip.sha512
$ shasum -c apache-dubbo-incubating-${release_version}-bin-release.zip.sha512
```
@@ -267,7 +273,7 @@ $ shasum -c
apache-dubbo-incubating-${release_version}-bin-release.zip.sha512
- Release candidates match with corresponding tags, you can find tag link and
hash in vote email.
- check the version number in pom.xml are the same
- check there are no extra files or directories in the source package, for
example, no empty directories or useless log files.
- `diff -r a rc_dir tag_dir`
+ `diff -r rc_dir tag_dir`
- check the top n tag commits, dive into the related files and check if the
source package has the same changes
3. Unzip apache-dubbo-incubating-${release_version}-bin-release.zip and check:
@@ -326,6 +332,6 @@ The Apache Dubbo (Incubating) Team
## Complete Maven Convenient Binary release（Optional）
-**apache.repository.org The permissions of the nexus repository have been
applied, see [jira](https://issues.apache.org/jira/browse/INFRA-16451)。**
+**[apache.repository.org](https://repository.apache.org/) The permissions of
the nexus repository have been applied, see
[jira](https://issues.apache.org/jira/browse/INFRA-16451)。**
-The artifacts that were previously published to the maven repository are in
the staging state. Log in to apache.repository.org with the Apache id and
release it.
+The artifacts that were previously published to the maven repository are in
the staging state. Log in to
[apache.repository.org](https://repository.apache.org/) with the Apache id and
release it.
