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 281ba4c Polish release document.
281ba4c is described below
commit 281ba4cb4a68477adfa490b752868ce75c95569f
Author: Huxing Zhang <[email protected]>
AuthorDate: Thu Jan 17 15:22:50 2019 +0800
Polish release document.
---
blog/en-us/prepare-an-apache-release.md | 16 ++++++++++------
1 file changed, 10 insertions(+), 6 deletions(-)
diff --git a/blog/en-us/prepare-an-apache-release.md
b/blog/en-us/prepare-an-apache-release.md
index 692f286..d6b91f0 100644
--- a/blog/en-us/prepare-an-apache-release.md
+++ b/blog/en-us/prepare-an-apache-release.md
@@ -154,25 +154,29 @@ modifications and taggings related to ${release_version}
Release Candidates are
- verify with dryRun
```shell
- $ mvn release:prepare -Papache-release -Darguments="-DskipTests"
-DautoVersionSubmodules=true -Dusername=YOUR GITHUB ID -DdryRun=true
+ $ mvn release:prepare -Prelease -Darguments="-Dmaven.test.skip=true"
-DautoVersionSubmodules=true -Dusername=YOUR GITHUB ID -DdryRun=true
```
- After verification, run release:prepare
```shell
$ mvn release:clean
- $ mvn release:prepare -Papache-release -Darguments="-DskipTests"
-DautoVersionSubmodules=true -Dusername=YOUR GITHUB ID
+ $ mvn release:prepare -Prelease -Darguments="-Dmaven.test.skip=true"
-DautoVersionSubmodules=true -Dusername=YOUR GITHUB ID
```
+ > If you are promted to input password for pushing to GitHub (basically
including adding new commits and tags), do not input your login password of
GitHub. Use `Personal access tokens` instead. You can go to
https://github.com/settings/profile, click `Developer settings` -> `Personal
access tokens`, and generate a new token if not.
+
+
+
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
+ 1. source-release.zip and bin-release.zip are generated under
dubbo-distribution directory, please unzip it and check the file structure
+ 2. The version tag has been push to github repository, you will see a
commit called `[maven-release-plugin] prepare release dubbo-x.x.x` were added
+ 3. The branch version is upgraded to ${release_version+1}-SNAPSHOT
automatically and the modifications are pushed to the github repository, you
will see a commit called `[maven-release-plugin] prepare for next development
iteration` were added
- Run release:perform, make an offical release
```shell
- $ mvn -Prelease release:perform -Darguments="-DskipTests"
-DautoVersionSubmodules=true -Dusername=YOUR GITHUB ID
+ $ mvn -Prelease release:perform -Darguments="-Dmaven.test.skip=true"
-DautoVersionSubmodules=true -Dusername=YOUR GITHUB ID
```
All artifacts are released to configured remote maven central repository,
in staging state
