This is an automated email from the ASF dual-hosted git repository.
pengys pushed a commit to branch asf/5.0-alpha/release
in repository https://gitbox.apache.org/repos/asf/incubator-skywalking.git
The following commit(s) were added to refs/heads/asf/5.0-alpha/release by this
push:
new f4bbdab Update How-to-release.md
f4bbdab is described below
commit f4bbdabb89d2b9253d9dfded02d822bd03a83437
Author: 彭勇升 pengys <[email protected]>
AuthorDate: Mon Mar 19 11:01:49 2018 +0800
Update How-to-release.md
---
docs/en/How-to-release.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/docs/en/How-to-release.md b/docs/en/How-to-release.md
index 87a4cac..7cdba3e 100644
--- a/docs/en/How-to-release.md
+++ b/docs/en/How-to-release.md
@@ -36,12 +36,12 @@ mvn clean install -Papache-release (this will build
artifacts, sources and sign)
## Prepare the release
```
mvn release:clean
-mvn release:prepare
+mvn release:prepare -DautoVersionSubmodules=true
```
## Stage the release for a vote
```
-mvn release:perform
+mvn release:perform -DskipTests
```
The release will automatically be inserted into a temporary staging repository
for you.
@@ -170,9 +170,9 @@ All PPMC members and committers should check these before
vote +1.
1. Source code and distribution package
(apache-skywalking-incubating-x.y.z.src.tar.gz,
apache-skywalking-incubating-x.y.z.tar.gz,
apache-skywalking-incubating-x.y.z.zip)
`in svn.apache.org` with .asc, .sha512
1. `LICENSE` and `NOTICE` are in Source code and distribution package.
-1. Check `shasum`
+1. Check `shasum -c apache-skywalking-apm-incubating-x.y.z-src.tgz.sha512`
1. Build distribution from source code package
(apache-skywalking-incubating-x.y.z.src.tar.gz) by following this
[doc](https://github.com/apache/incubator-skywalking/blob/master/docs/en/How-to-build.md#build-from-apache-source-codes).
1. Apache RAT check. Run `mvn apache-rat:check`.
## Call for a vote in Apache IPMC
-Call a vote in `[email protected]`
\ No newline at end of file
+Call a vote in `[email protected]`
--
To stop receiving notification emails like this one, please contact
[email protected].
