You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@servicecomb.apache.org by ni...@apache.org on 2020/02/22 09:17:07 UTC

[servicecomb-website] branch asf-site updated (a2eef2e -> d6fd673)

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

ningjiang pushed a change to branch asf-site
in repository https://gitbox.apache.org/repos/asf/servicecomb-website.git.


    from a2eef2e  Publish the website
     add ccd0e0a  [SCB-1778] update java-chassis release guide and verification guide
     add 75d0dbf  [SCB-1778] add notes to delete temporary artifacts
     new 1863556  Merge branch 'master' into asf-site
     new d6fd673  Publish the website

The 2 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.


Summary of changes:
 _developers/cn/release_guide.md                    | 133 ++++++++++++---------
 _developers/cn/release_validation_guide.md         |  13 +-
 _developers/release_guide.md                       | 128 ++++++++++++++------
 _developers/release_validation_guide.md            |  11 +-
 content/cn/developers/release-guide/index.html     | 101 +++++++++-------
 .../developers/release-validation-guide/index.html |  13 +-
 content/developers/release-guide/index.html        | 132 +++++++++++++-------
 .../developers/release-validation-guide/index.html |  11 +-
 content/feed.xml                                   |   2 +-
 9 files changed, 342 insertions(+), 202 deletions(-)


[servicecomb-website] 01/02: Merge branch 'master' into asf-site

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

ningjiang pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/servicecomb-website.git

commit 18635569434086b566768d67e351a1d7c79021f8
Merge: a2eef2e 75d0dbf
Author: Willem Jiang <wi...@gmail.com>
AuthorDate: Sat Feb 22 17:15:40 2020 +0800

    Merge branch 'master' into asf-site

 _developers/cn/release_guide.md            | 133 ++++++++++++++++-------------
 _developers/cn/release_validation_guide.md |  13 +--
 _developers/release_guide.md               | 128 ++++++++++++++++++---------
 _developers/release_validation_guide.md    |  11 +--
 4 files changed, 180 insertions(+), 105 deletions(-)


[servicecomb-website] 02/02: Publish the website

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

ningjiang pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/servicecomb-website.git

commit d6fd673a38da1f7a1699089c66809de313f0fbdf
Author: Willem Jiang <wi...@gmail.com>
AuthorDate: Sat Feb 22 17:16:39 2020 +0800

    Publish the website
---
 content/cn/developers/release-guide/index.html     | 101 +++++++++-------
 .../developers/release-validation-guide/index.html |  13 +-
 content/developers/release-guide/index.html        | 132 ++++++++++++++-------
 .../developers/release-validation-guide/index.html |  11 +-
 content/feed.xml                                   |   2 +-
 5 files changed, 162 insertions(+), 97 deletions(-)

diff --git a/content/cn/developers/release-guide/index.html b/content/cn/developers/release-guide/index.html
index 90e34b7..bdb5e89 100644
--- a/content/cn/developers/release-guide/index.html
+++ b/content/cn/developers/release-guide/index.html
@@ -611,16 +611,36 @@ gvt restore
 </ol>
 
 <h2 id="发行java-chassis">发行Java-Chassis</h2>
+<p>发布版本前,首先确定该版本所有的 apache issues 都已经关闭, 并且
+登录 <a href="https://issues.apache.org/jira/projects/SCB">apache issue 网站</a>, 点击发布, 生成该版本的 release notes.</p>
 
-<p><strong><em>准备和校验发行包</em></strong></p>
+<p><strong><em>准备待发布版本</em></strong></p>
+
+<p>clone 需要发布版本的分支到开发环境(比如 master), 修改版本号, 并提交代码到仓库。假设当前版本为 <code class="highlighter-rouge">2.0.0-SNAPSHOT</code>,发布版
+本为 <code class="highlighter-rouge">2.0.0</code>。</p>
+
+<p>执行:
+```shell script
+mvn versions:set -DgenerateBackupPoms=false -DnewVersion=2.0.0</p>
+<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>
+然后执行:
+```shell script
+mvn clean install -Pit
+</code></pre></div></div>
+
+<p>如果编译成功,可以提交PR,代码检视通过后合入仓库。</p>
+
+<p><strong><em>进行软件包发布</em></strong></p>
+
+<p>需要准备 Linux 开发环境,并确保网络能够往 maven 中央库上传文件。</p>
 
 <ol>
   <li>如果<code class="highlighter-rouge">~/.gnupg</code>中没有GPG密钥文件,则将GPG密钥文件拷贝至<code class="highlighter-rouge">~/.gnupg</code>文件夹。
-    <div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>  gpg.conf
-  pubring.gpg
-  random_seed
-  secring.gpg
-  trustdb.gpg
+    <div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code> gpg.conf
+ pubring.gpg
+ random_seed
+ secring.gpg
+ trustdb.gpg
 </code></pre></div>    </div>
   </li>
   <li>
@@ -630,28 +650,21 @@ gvt restore
     <p>更新<code class="highlighter-rouge">~/.m2/settings.xml</code>文件中的Apache帐户用户名和密码。</p>
   </li>
   <li>克隆java-chassis代码
-    <div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>git clone https://github.com/apache/servicecomb-java-chassis.git
+    <div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code> git clone https://github.com/apache/servicecomb-java-chassis.git
 </code></pre></div>    </div>
   </li>
-  <li>使用以下perl命令,替换所有pom.xml文件中的版本号并提交改动至本地
-    <div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>find . -name 'pom.xml'|xargs perl -pi -e 's/1.0.0-m2-SNAPSHOT/1.0.0-m2/g'
-</code></pre></div>    </div>
-  </li>
-  <li>
-    <p>在需要release的分支上打上准备发布版本的标签。</p>
-  </li>
   <li>运行以下命令
-    <div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>mvn clean deploy -DskipTests -Prelease -Pdistribution -Ppassphrase
+    <div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code> mvn clean deploy -DskipTests -Prelease -Pdistribution -Ppassphrase
 </code></pre></div>    </div>
   </li>
   <li>
-    <p>如果执行失败,需要解决问题,从步骤7重新开始。</p>
+    <p>如果执行失败,需要解决问题。 并参考第7步<code class="highlighter-rouge">drop</code>临时仓库,重新执行第5步。</p>
   </li>
   <li>
-    <p>如果步骤7命令执行成功,则所有的jar包都已经成功上传至maven临时仓库。<br />
-使用apache帐号登录到<a href="https://repository.apache.org/">Apache Nexus</a>,点击“Staging Repositories”,搜索“servicecomb”,根据时间找到最近的java-chassis相关的记录,close该条记录,得到maven临时仓库的链接,例如:<code class="highlighter-rouge">https://repository.apache.org/content/repositories/orgapacheservicecomb-1385</code></p>
+    <p>如果步骤5命令执行成功,则所有的jar包都已经成功上传至maven临时仓库。<br />
+使用apache帐号登录到<a href="https://repository.apache.org/">Apache Nexus</a>,点击“Staging Repositories”,搜索“servicecomb”,根据时间找到最近的java-chassis相关的记录,close该条记录,得到maven临时仓库的链接,例如:<code class="highlighter-rouge">https://repository.apache.org/content/repositories/orgapacheservicecomb-1385</code>。</p>
   </li>
-  <li>将release分支以及标签分别push至主仓库。</li>
+  <li>在 servicecomb-java-chassis 的 github 的 release 页面,点击 release, 发布 pre release 版本, 打上 tag 。</li>
 </ol>
 
 <p><strong><em>给发行包签名</em></strong></p>
@@ -675,14 +688,14 @@ gvt restore
   <code class="highlighter-rouge">sha512sum -b apache-servicecomb-java-chassis-distribution-1.2.0-bin.zip &gt; apache-servicecomb-java-chassis-distribution-1.2.0-bin.zi.sha512</code><br />
   <code class="highlighter-rouge">sha512sum -b apache-servicecomb-java-chassis-distribution-1.2.0-src.zip &gt; apache-servicecomb-java-chassis-distribution-1.2.0-src.zip.sha512</code></p>
   </li>
-  <li>将步骤11、12、13相关的文件,上传到<a href="https://dist.apache.org/repos/dist/dev/servicecomb/servicecomb-java-chassis/">Apache开发仓库</a>.<br />
+  <li>将上述步骤相关的文件,上传到<a href="https://dist.apache.org/repos/dist/dev/servicecomb/servicecomb-java-chassis/">Apache开发仓库</a>.<br />
   SVN命令:
-    <div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>  svn co https://dist.apache.org/repos/dist/dev/servicecomb/servicecomb-java-chassis
-  cd serviecomb-java-chassis
-  mkdir -p 1.2.0/rc01
-  cp xxx/* 1.2.0/rc01
-  svn add 1.2.0/rc01
-  svn ci 1.2.0/rc01
+    <div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code> svn co https://dist.apache.org/repos/dist/dev/servicecomb/servicecomb-java-chassis
+ cd serviecomb-java-chassis
+ mkdir -p 1.2.0/rc01
+ cp xxx/* 1.2.0/rc01
+ svn add 1.2.0
+ svn ci 1.2.0
 </code></pre></div>    </div>
   </li>
   <li>从SVN下载发行包,验证签名和校验。</li>
@@ -695,35 +708,41 @@ gvt restore
     <p>发送投票邮件至 <strong><em>dev@servicecomb.apache.org</em></strong>, 发起PMC批准.</p>
   </li>
   <li>
-    <p>等待72小时,或者获得3票+1并且没有-1。如果有-1票,修正问题,并删除主仓库的release版本对应的标签,并从<strong><em>第1步</em></strong>重新开始。</p>
+    <p>等待72小时,或者获得3票+1并且没有-1。如果有-1票,修正问题,重新开始版本发布流程(视具体的失败情况,可能
+需要重新生成 release notes,删除svn临时文件,删除临时<code class="highlighter-rouge">Staging repositories</code>等)。</p>
   </li>
   <li>
     <p>将投票结果发布到dev@servicecomb.apache.org。</p>
   </li>
 </ol>
 
-<p><strong><em>通告</em></strong></p>
+<p><strong><em>更新文档和通告</em></strong></p>
 
 <ol>
-  <li>将<a href="https://dist.apache.org/repos/dist/dev">dev</a>的文件移动到<a href="https://dist.apache.org/repos/dist/release">release</a>目录中,同时确认已经被存档,同时更新网站上相关链接。
-同时删除<a href="https://dist.apache.org/repos/dist/dev/servicecomb/servicecomb-java-chassis/">Apache开发仓库</a>中的目录
-    <div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>svn rm -r 1.2.0
-checkin?
+  <li>
+    <p>在 servicecomb-java-chassis 的 github 的 release 页面,将 pre release 修改为正式 release。完成 release notes书写。</p>
+  </li>
+  <li>将<a href="https://dist.apache.org/repos/dist/dev">dev</a>的文件移动到<a href="https://dist.apache.org/repos/dist/release">release</a>目录中。
+    <div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code> cp dev/servicecomb/servicecomb-java-chassis/2.0.0/* release/servicecomb/servicecomb-java-chassis/2.0.0/
+ cd release/servicecomb/servicecomb-java-chassis/
+ svn add 2.0.0
+ svn ci 2.0.0
 </code></pre></div>    </div>
-    <p>使用apache帐号登录到<a href="https://repository.apache.org/">Apache Nexus</a>,点击“Staging Repositories”,搜索“servicecomb”,选中java-chassis相关的所有记录,点击“Drop”。</p>
-
-    <p>使用apache帐号登录到<a href="https://repository.apache.org/">Apache Nexus</a>,点击“Staging Repositories”,搜索“servicecomb”,找到需要发布的java-chassis记录,点击“Release”。</p>
+    <p>同时删除<a href="https://dist.apache.org/repos/dist/dev">dev</a>的临时内容。</p>
+    <div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code> svn rm -r 1.2.0
+ svn ci .
+</code></pre></div>    </div>
+  </li>
+  <li>
+    <p>使用apache帐号登录到<a href="https://repository.apache.org/">Apache Nexus</a>,点击“Staging Repositories”,搜索“servicecomb”,
+找到需要发布的java-chassis记录,点击“Release”。 如果由其他临时“Staging Repositories”,可以点击“Drop”一并删除。</p>
   </li>
   <li>
     <p>等待24小时,让所有镜像同步。</p>
   </li>
   <li>
-    <p>上传发行页面至ServiceComb网站。
-   fork https://github.com/apache/servicecomb-website/
-   1.总版本,url
-   2.java-chassis的RN和download(url)
-   3.中文、英文
-   PR</p>
+    <p>更新官网发布信息。 修改内容可以参考 <a href="https://github.com/apache/servicecomb-website/pull/210">1.3.0 RP</a>
+或者 <a href="https://github.com/apache/servicecomb-website/pull/240">2.0.0 RP</a></p>
   </li>
   <li>发送发行通告邮件到dev@servicecomb.apache.org, announce@apache.org。</li>
 </ol>
diff --git a/content/cn/developers/release-validation-guide/index.html b/content/cn/developers/release-validation-guide/index.html
index 23241ee..a866bc8 100644
--- a/content/cn/developers/release-validation-guide/index.html
+++ b/content/cn/developers/release-validation-guide/index.html
@@ -546,12 +546,12 @@
 
 <p>使用<code class="highlighter-rouge">cd</code>命令切换到解压出来的源代码根目录下,执行:</p>
 
-<div class="language-bash highlighter-rouge"><div class="highlight"><pre class="highlight"><code>mvn clean <span class="nb">install</span> <span class="nt">-Pdocker</span> <span class="nt">-Pit</span>
+<div class="language-bash highlighter-rouge"><div class="highlight"><pre class="highlight"><code>mvn clean <span class="nb">install</span> <span class="nt">-Pdocker</span> <span class="nt">-Pit</span> <span class="nt">-Pdemo-run-release</span>
 </code></pre></div></div>
 
 <blockquote>
   <p>提示:如果如果验证环境操作系统是Windows:</p>
-  <div class="language-bash highlighter-rouge"><div class="highlight"><pre class="highlight"><code>mvn clean <span class="nb">install</span> <span class="nt">-Pdocker</span> <span class="nt">-Pit</span> <span class="nt">-Pdocker-machine</span>
+  <div class="language-bash highlighter-rouge"><div class="highlight"><pre class="highlight"><code>mvn clean <span class="nb">install</span> <span class="nt">-Pdocker</span> <span class="nt">-Pit</span> <span class="nt">-Pdocker-machine</span> <span class="nt">-Pdemo-run-release</span>
 </code></pre></div>  </div>
 </blockquote>
 
@@ -605,12 +605,12 @@
 
 <p>一切就绪后,使用<code class="highlighter-rouge">cd</code>命令切换到<strong>源代码demo目录(注意不是根目录)下</strong>,执行:</p>
 
-<div class="language-bash highlighter-rouge"><div class="highlight"><pre class="highlight"><code>mvn clean <span class="nb">install</span> <span class="nt">-Pdocker</span> <span class="nt">-Pstaging</span>
+<div class="language-bash highlighter-rouge"><div class="highlight"><pre class="highlight"><code>mvn clean <span class="nb">install</span> <span class="nt">-Pdocker</span> <span class="nt">-Pstaging</span> <span class="nt">-Pit</span> <span class="nt">-Pdemo-run-release</span>
 </code></pre></div></div>
 
 <blockquote>
   <p>提示:如果如果验证环境操作系统是Windows:</p>
-  <div class="language-bash highlighter-rouge"><div class="highlight"><pre class="highlight"><code>mvn clean <span class="nb">install</span> <span class="nt">-Pdocker</span> <span class="nt">-Pstaging</span> <span class="nt">-Pdocker-machine</span>
+  <div class="language-bash highlighter-rouge"><div class="highlight"><pre class="highlight"><code>mvn clean <span class="nb">install</span> <span class="nt">-Pdocker</span> <span class="nt">-Pstaging</span> <span class="nt">-Pdocker-machine</span>  <span class="nt">-Pit</span> <span class="nt">-Pdemo-run-release</span>
 </code></pre></div>  </div>
 </blockquote>
 
@@ -649,7 +649,10 @@ git checkout 1.x
 <p>等待所有的测试通过,依据配置环境不同,约耗时5~10分钟。</p>
 
 <h3 id="验证samples是否正确可选">验证Samples是否正确(可选)</h3>
-<p>在源代码的sample下有很多例子,可以任选几个测试,例如使用BMI做验证;sample验证的方法请参见对应目录下README.md中的说明即可。</p>
+
+<p>下载 <a href="https://github.com/apache/servicecomb-samples">samples 代码</a>, 由于 samples 较多, 可以选择部分
+进行验证, 详细参考每一个 sample 提供的 README 文件。</p>
+
 
         
       </section>
diff --git a/content/developers/release-guide/index.html b/content/developers/release-guide/index.html
index d88fe3f..9efb863 100644
--- a/content/developers/release-guide/index.html
+++ b/content/developers/release-guide/index.html
@@ -602,101 +602,143 @@ gvt restore
 </ol>
 
 <h2 id="major-steps-for-doing-java-chassis-release">Major Steps for doing Java-Chassis Release</h2>
+<p>Before release, make sure all apache issues are closed. Log in
+ <a href="https://issues.apache.org/jira/projects/SCB">apache issue website</a>, click <code class="highlighter-rouge">release</code> and generate release notes.</p>
 
-<p><strong><em>Make and Verify the Release</em></strong></p>
+<p><strong><em>Prepare the release code</em></strong></p>
+
+<p>clone java-chassis code to your development environment, change version to release version and push to github.
+Assume code version is <code class="highlighter-rouge">2.0.0-SNAPSHOT</code> and release version is <code class="highlighter-rouge">2.0.0</code>.</p>
+
+<p>Run:
+```shell script
+mvn versions:set -DgenerateBackupPoms=false -DnewVersion=2.0.0</p>
+<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>
+Then:
+```shell script
+mvn clean install -Pit
+</code></pre></div></div>
+
+<p>If the build is successful, submit a PR and merge code after review.</p>
+
+<p><strong><em>Release maven artifacts</em></strong></p>
+
+<p>Prepare Linux environment, and make sure can upload artifacts to maven central.</p>
 
 <ol>
-  <li>Clone the java-chassis code.
-    <div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>git clone https://github.com/apache/servicecomb-java-chassis.git
+  <li>Copy GPG keys to <code class="highlighter-rouge">~/.gnupg</code>
+    <div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code> gpg.conf
+ pubring.gpg
+ random_seed
+ secring.gpg
+ trustdb.gpg
 </code></pre></div>    </div>
   </li>
-  <li>Cut the release using perl command to replace all the versions in pom.xml files
-    <div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>find . -name 'pom.xml'|xargs perl -pi -e 's/1.0.0-m2-SNAPSHOT/1.0.0-m2/g'
-</code></pre></div>    </div>
-  </li>
-  <li>
-    <p>Create a Tag from the master branch using the version number.</p>
-  </li>
-  <li>
-    <p>Clear all the redundant servicecomb releases in repository.apache.org</p>
-  </li>
   <li>
-    <p>Add the keys in a reference folder.</p>
+    <p>Update PGR password in <code class="highlighter-rouge">~/.m2/settings.xml</code></p>
   </li>
   <li>
-    <p>Update the key path and passphrase in ~/.m2/settings.xml file.</p>
+    <p>Update apache maven server user name and password in <code class="highlighter-rouge">~/.m2/settings.xml</code></p>
   </li>
-  <li>
-    <p>Update the apache account username and password in the settings file.</p>
+  <li>clone java-chassis
+    <div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code> git clone https://github.com/apache/servicecomb-java-chassis.git
+</code></pre></div>    </div>
   </li>
-  <li>Run the maven deploy command.
-    <div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>mvn deploy -DskipTests -Prelease -Pdistribution -Ppassphrase
+  <li>Run
+    <div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code> mvn clean deploy -DskipTests -Prelease -Pdistribution -Ppassphrase
 </code></pre></div>    </div>
   </li>
   <li>
-    <p>Once every thing is uploaded then use the staging repo to verify the build using Company workshop.</p>
+    <p>If failed in step 5, <code class="highlighter-rouge">drop</code> the temporary repository in apache Nexus and start from step 5 again.</p>
   </li>
   <li>
-    <p>Share the staging repo with peers to verify on different OS and machines using the demo.</p>
+    <p>If step 5 is successful, all artifacts are uploaded to a temporary repository. Using your apache account and 
+log in to  <a href="https://repository.apache.org/">Apache Nexus</a>. Click  <code class="highlighter-rouge">Staging Repositories</code>, search <code class="highlighter-rouge">servicecomb</code>,
+find the latest repository, click “close”, and get the staging repository link like <code class="highlighter-rouge">https://repository.apache.org/content/repositories/orgapacheservicecomb-1385</code></p>
   </li>
-  <li>
-    <p>If everything is fine then push the tag to master.</p>
-  </li>
-  <li>Close the staging repo is apache repositories</li>
+  <li>In servicecomb-java-chassis  release page,click release, do a <code class="highlighter-rouge">pre release</code></li>
 </ol>
 
-<p><strong><em>Sign the Releases</em></strong></p>
+<p><strong><em>Sign the distributions</em></strong></p>
 
 <ol>
   <li>
-    <p>Download the source code and distribution from the staging repo.</p>
+    <p>Download binary distributions from the temporary repository.
+  e.g.<br />
+  <code class="highlighter-rouge">https://repository.apache.org/content/repositories/orgapacheservicecomb-1385/org/apache/servicecomb/apache-servicecomb-java-chassis-distribution/1.2.0/apache-servicecomb-java-chassis-distribution-1.2.0-bin.zip</code><br />
+  <code class="highlighter-rouge">https://repository.apache.org/content/repositories/orgapacheservicecomb-1385/org/apache/servicecomb/apache-servicecomb-java-chassis-distribution/1.2.0/apache-servicecomb-java-chassis-distribution-1.2.0-bin.zip.asc</code></p>
   </li>
   <li>
-    <p>Sign the 2 releases(distribution, src) and checksum.</p>
+    <p>Download source distributions from the temporary repository.
+  e.g.
+  <code class="highlighter-rouge">https://repository.apache.org/content/repositories/orgapacheservicecomb-1385/org/apache/servicecomb/apache-servicecomb-java-chassis-distribution/1.2.0/apache-servicecomb-java-chassis-distribution-1.2.0-src.zip</code><br />
+  <code class="highlighter-rouge">https://repository.apache.org/content/repositories/orgapacheservicecomb-1385/org/apache/servicecomb/apache-servicecomb-java-chassis-distribution/1.2.0/apache-servicecomb-java-chassis-distribution-1.2.0-src.zip.asc</code></p>
   </li>
   <li>
-    <p>Create a new directory <a href="https://dist.apache.org/repos/dist/dev/servicecomb/servicecomb-java-chassis/">Apache dev Release SVN</a> with release package name and release candidate number. (for example : if you want to release 1.0.0-m2 and this is the first attempt of the release then the folder structure will be <code class="highlighter-rouge">1.0.0-m2/rc01</code>)</p>
+    <p>generate checksum.
+  e.g.
+  <code class="highlighter-rouge">sha512sum -b apache-servicecomb-java-chassis-distribution-1.2.0-bin.zip &gt; apache-servicecomb-java-chassis-distribution-1.2.0-bin.zi.sha512</code><br />
+  <code class="highlighter-rouge">sha512sum -b apache-servicecomb-java-chassis-distribution-1.2.0-src.zip &gt; apache-servicecomb-java-chassis-distribution-1.2.0-src.zip.sha512</code></p>
   </li>
-  <li>
-    <p>Upload the release to  directory created in last step.</p>
-  </li>
-  <li>
-    <p>Download all the releases from SVN and verify the signature and checksum.</p>
+  <li>upload all file to <a href="https://dist.apache.org/repos/dist/dev/servicecomb/servicecomb-java-chassis/">Apache development svn</a>.<br />
+  Run
+    <div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code> svn co https://dist.apache.org/repos/dist/dev/servicecomb/servicecomb-java-chassis
+ cd serviecomb-java-chassis
+ mkdir -p 1.2.0/rc01
+ cp xxx/* 1.2.0/rc01
+ svn add 1.2.0
+ svn ci 1.2.0
+</code></pre></div>    </div>
   </li>
+  <li>download the files and verify the sign.</li>
 </ol>
 
-<p><strong><em>PMC approval</em></strong></p>
+<p><strong><em>Sending mail for permission</em></strong></p>
 
 <ol>
   <li>
-    <p>Send the voting mail in dev@servicecomb.apache.org for PMC approval.</p>
+    <p>Send mail to <code class="highlighter-rouge">dev@servicecomb.apache.org</code> and waiting for voting result.</p>
   </li>
   <li>
-    <p>Wait for 72 hours or unless you get 3 +1 binding vote with no -1 vote. If you get even one -1 binding vote then fix the issue and start again from Step 1.</p>
+    <p>Waiting 72 hours and if got three + 1 and no -1, the voting is successful. If there are some problems,
+start a new round of release. (According to the problem, please notice to clean up release notes,
+temporary svn files, and temporary stating repositories. )</p>
   </li>
   <li>
-    <p>Publish the result of the vote in dev@servicecomb.apache.org.</p>
+    <p>Send the voting result to <code class="highlighter-rouge">dev@servicecomb.apache.org</code></p>
   </li>
 </ol>
 
-<p><strong><em>Announcements</em></strong></p>
+<p><strong><em>Update documents and announcements</em></strong></p>
 
 <ol>
   <li>
-    <p>Upload the releases to <a href="https://dist.apache.org/repos/dist/release/servicecomb/servicecomb-java-chassis/">Apache release repository</a>.</p>
+    <p>In servicecomb-java-chassis  github release page,set <code class="highlighter-rouge">pre release</code> to <code class="highlighter-rouge">formal release</code> and write release notes.</p>
   </li>
-  <li>
-    <p>Wait for 24 hours to replicate the release in all the mirrors.</p>
+  <li>Move <a href="https://dist.apache.org/repos/dist/dev">dev</a> to <a href="https://dist.apache.org/repos/dist/release">release</a>
+    <div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code> cp dev/servicecomb/servicecomb-java-chassis/2.0.0/* release/servicecomb/servicecomb-java-chassis/2.0.0/
+ cd release/servicecomb/servicecomb-java-chassis/
+ svn add 2.0.0
+ svn ci 2.0.0
+</code></pre></div>    </div>
+    <p>And delete <a href="https://dist.apache.org/repos/dist/dev">dev</a></p>
+    <div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code> svn rm -r 1.2.0
+ svn ci .
+</code></pre></div>    </div>
   </li>
   <li>
-    <p>Delete old releases from <a href="https://dist.apache.org/repos/dist/dev">dev</a> and [release] (https://dist.apache.org/repos/dist/release) and check for the old release in archive, update the same links in the website for old releases.</p>
+    <p>Log in to <a href="https://repository.apache.org/">Apache Nexus</a>, find <code class="highlighter-rouge">Staging Repositories</code> and search 
+<code class="highlighter-rouge">servicecomb</code>,find the last <code class="highlighter-rouge">closed</code> repository, and click <code class="highlighter-rouge">release</code>. If there are any temporary <code class="highlighter-rouge">Staging Repositories</code>,
+<code class="highlighter-rouge">drop</code> them.</p>
   </li>
   <li>
-    <p>Upload the release page of ServiceComb Website.</p>
+    <p>Waiting for 24 hour for all mirror in sync.</p>
   </li>
   <li>
-    <p>Send the announcement mails to dev@servicecomb.apache.org, announce@apache.org</p>
+    <p>Update the servicecomb-website, see <a href="https://github.com/apache/servicecomb-website/pull/210">1.3.0 RP</a>
+or <a href="https://github.com/apache/servicecomb-website/pull/240">2.0.0 RP</a></p>
   </li>
+  <li>Send announcements to dev@servicecomb.apache.org, announce@apache.org。</li>
 </ol>
 
 <h2 id="major-steps-for-doing-saga-release">Major Steps for doing Saga Release</h2>
diff --git a/content/developers/release-validation-guide/index.html b/content/developers/release-validation-guide/index.html
index 1b4cc59..eb4808f 100644
--- a/content/developers/release-validation-guide/index.html
+++ b/content/developers/release-validation-guide/index.html
@@ -512,12 +512,12 @@
 
 <p>Run test case under source code root:</p>
 
-<div class="language-bash highlighter-rouge"><div class="highlight"><pre class="highlight"><code>mvn clean <span class="nb">install</span> <span class="nt">-Pdocker</span> <span class="nt">-Pit</span>
+<div class="language-bash highlighter-rouge"><div class="highlight"><pre class="highlight"><code>mvn clean <span class="nb">install</span> <span class="nt">-Pdocker</span> <span class="nt">-Pit</span> <span class="nt">-Pdemo-run-release</span>
 </code></pre></div></div>
 
 <blockquote>
   <p>Hint: If the OS of environment is Windows:</p>
-  <div class="language-bash highlighter-rouge"><div class="highlight"><pre class="highlight"><code>mvn clean <span class="nb">install</span> <span class="nt">-Pdocker</span> <span class="nt">-Pit</span> <span class="nt">-Pdocker-machine</span>
+  <div class="language-bash highlighter-rouge"><div class="highlight"><pre class="highlight"><code>mvn clean <span class="nb">install</span> <span class="nt">-Pdocker</span> <span class="nt">-Pit</span> <span class="nt">-Pdocker-machine</span> <span class="nt">-Pdemo-run-release</span>
 </code></pre></div>  </div>
 </blockquote>
 
@@ -571,12 +571,12 @@
 
 <p>After that, enter <strong>demo folder under the source code(not root folder of source code)</strong> and run:</p>
 
-<div class="language-bash highlighter-rouge"><div class="highlight"><pre class="highlight"><code>mvn clean <span class="nb">install</span> <span class="nt">-Pdocker</span> <span class="nt">-Pstaging</span>
+<div class="language-bash highlighter-rouge"><div class="highlight"><pre class="highlight"><code>mvn clean <span class="nb">install</span> <span class="nt">-Pdocker</span> <span class="nt">-Pstaging</span> <span class="nt">-Pdemo-run-release</span>
 </code></pre></div></div>
 
 <blockquote>
   <p>Hint: If the OS of environment is Windows:</p>
-  <div class="language-bash highlighter-rouge"><div class="highlight"><pre class="highlight"><code>mvn clean <span class="nb">install</span> <span class="nt">-Pdocker</span> <span class="nt">-Pstaging</span> <span class="nt">-Pdocker-machine</span>
+  <div class="language-bash highlighter-rouge"><div class="highlight"><pre class="highlight"><code>mvn clean <span class="nb">install</span> <span class="nt">-Pdocker</span> <span class="nt">-Pstaging</span> <span class="nt">-Pdocker-machine</span> <span class="nt">-Pdemo-run-release</span>
 </code></pre></div>  </div>
 </blockquote>
 
@@ -615,7 +615,8 @@ git checkout 1.x
 <p>Wait all test case check passed, may use 5~10 minutes.</p>
 
 <h3 id="verify-samplesoptional">Verify Samples(Optional)</h3>
-<p>In samples folder of source code, there are many java chassis sample, we can choose some of them do verification such as BMI; you can read README.md in each sample in order to known how to run.</p>
+<p>Download <a href="https://github.com/apache/servicecomb-samples">samples code</a>. There are many samples here, choose 
+some of them and change the version and do verifications. See each README of samples for details.</p>
 
         
       </section>
diff --git a/content/feed.xml b/content/feed.xml
index e7d9d9d..7507fe4 100644
--- a/content/feed.xml
+++ b/content/feed.xml
@@ -1,4 +1,4 @@
-<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="3.8.5">Jekyll</generator><link href="/feed.xml" rel="self" type="application/atom+xml" /><link href="/" rel="alternate" type="text/html" /><updated>2020-02-21T00:05:21+08:00</updated><id>/feed.xml</id><title type="html">Apache ServiceComb</title><subtitle>The homepage of ServiceComb</subtitle><author><name>{&quot;name&quot;=&gt;nil, &quot;avatar&quot;=&gt;&quot [...]
+<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="3.8.5">Jekyll</generator><link href="/feed.xml" rel="self" type="application/atom+xml" /><link href="/" rel="alternate" type="text/html" /><updated>2020-02-22T17:15:48+08:00</updated><id>/feed.xml</id><title type="html">Apache ServiceComb</title><subtitle>The homepage of ServiceComb</subtitle><author><name>{&quot;name&quot;=&gt;nil, &quot;avatar&quot;=&gt;&quot [...]
 
 &lt;p&gt;本次讲座得到广东工业大学计算机院学生会同学们的鼎力支持和参与。报名通道开放后,报名人数迅速达到150+,活动放在学校报告厅举办。即便在周日,同学们的热情仍然很高,给广东工业大学的同学们点赞。&lt;/p&gt;