WillemJiang closed pull request #78: [SCB-528] Translate release guide to 
Chinese
URL: https://github.com/apache/incubator-servicecomb-website/pull/78
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git a/_developers/cn/release_guide.md b/_developers/cn/release_guide.md
index e36b5e4..fe5b59a 100644
--- a/_developers/cn/release_guide.md
+++ b/_developers/cn/release_guide.md
@@ -1,234 +1,297 @@
 ---
-title: "Release guide for ServiceComb"
+title: "ServiceComb����ָ��"
 lang: cn
 ref: release_guide
 permalink: /cn/developers/release-guide/
-excerpt: "ServiceComb发版指南 介绍如何在Apache发版"
-last_modified_at: 2018-04-27T18:33:43+08:00
+excerpt: "ServiceComb����ָ�� ���������Apache����"
+last_modified_at:  2018-05-08T09:55:44+08:00
 author: Asif Siddiqui
-tags: [release]
+tags: [����]
 redirect_from:
   - /theme-setup/
 ---
 
+�������ҽ��������Apache�Ͻ���ServiceComb��Ŀ����.
 
-本文向大家介绍如何在Apache上进行ServiceComb项目发版.
+## ǰ��׼��
 
-## 前期准备
+1. ��ĿCIӦ���������ģ���ɫ�ģ���
+2. ȷ����ص���Ŀ�汾�š�
+3. ��Ϊ����Ĺ�������Ҫǩ������ȷ��ǩ������Կ��Ӧ��Կ�Ѿ�������������Կ��������
+4. ��ϤPOM�ļ��а汾������ص����á�
 
-1. 项目CI应该是正常的(绿色的)。
-2. 确定相关的项目版本号。
-3. 因为发版的过程中需要签名,请确保签名用的key的公钥是发布到公开的公钥服务器上的。
+## ����Maven
+ServiceComb 
Java-Chassis��Sagaʹ��Maven���а汾������������Ҫ�ڷ���ǰ��Maven����һЩ���á�
 
-## 发布Service-Center 需要做的步骤
+��ʹ��Maven�ѷ��а��������ֿ�֮ǰ������Ӧ����`~/.m2/settings.xml`�ļ���������ƷΪ��Ⱥ��д�ģ���������������Ա���޷��ύ��ͬ��Ʒ����SNAPSHOT�汾������Ŀ�ο���Maven��Ŀ���趨[ָ��](http://maven.apache.org/developers/committer-settings.html)�����ر�ע��[��������](http://maven.apache.org/guides/mini/guide-encryption.html)��
 
-***版本制作以及验证版本***
+```
+<settings>
+  ...
+  <servers>
+    <!-- Per http://maven.apache.org/developers/committer-settings.html -->
+
+    <!-- To publish a snapshot of some part of Maven -->
+    <server>
+      <id>apache.snapshots.https</id>
+      <username> <!-- YOUR APACHE LDAP USERNAME --> </username>
+      <password> <!-- YOUR APACHE LDAP PASSWORD --> </password>
+    </server>
+    <!-- To publish a website of some part of Maven -->
+    <server>
+      <id>apache.website</id>
+      <username> <!-- YOUR APACHE LDAP USERNAME --> </username>
+      <filePermissions>664</filePermissions>
+      <directoryPermissions>775</directoryPermissions>
+    </server>
+    <!-- To stage a release of some part of Maven -->
+    <server>
+      <id>apache.releases.https</id>
+      <username> <!-- YOUR APACHE LDAP USERNAME --> </username>
+      <password> <!-- YOUR APACHE LDAP PASSWORD --> </password>
+    </server>
+    <!-- To stage a website of some part of Maven -->
+    <server>
+      <id>stagingSite</id> <!-- must match hard-coded repository identifier in 
site:stage-deploy -->
+      <username> <!-- YOUR APACHE LDAP USERNAME --> </username>
+      <filePermissions>664</filePermissions>
+      <directoryPermissions>775</directoryPermissions>
+    </server>
+
+  </servers>
+  ...
+  <profiles>
+    <profile>
+      <id>apache-release</id>
+      <properties>
+        <gpg.useagent>false</gpg.useagent>
+        <gpg.passphrase><!-- YOUR GPG PASSPHRASE --></gpg.passphrase>
+        <test>false</test>
+      </properties>
+    </profile>
+
+  </profiles>
+...
+</settings>
+```
+
+## ����Service-Center
+
+***׼����У�鷢�а�***
 
-1. Clone the service-center code.
+1. ��¡service-center���롣
 ```
 g...@github.com:apache/incubator-servicecomb-service-center.git
 cd incubator-servicecomb-service-center
 gvt restore
 ```
 
-2. Create a Tag from the master branch based on the version number which needs 
to be released.
+2. ��master��֧�ϴ���׼�������汾�ı�ǩ��
 
-3. Run RAT tool to ensure no license issues are there, follow the guide over 
[here](https://github.com/apache/incubator-servicecomb-service-center/tree/master/docs/release)
+3. ����RAT���ߣ��������Դ�ļ�ͷ���кϷ���ASF����, 
��ο�[���ĵ�](https://github.com/apache/incubator-servicecomb-service-center/tree/master/docs/release)��
 
-4. Run the make_release.sh to make the release for windows and linux following 
the guide over 
[here](https://github.com/apache/incubator-servicecomb-service-center/tree/master/scripts/release).
+4. 
����`make_release.sh`�ű�����ο�[���ĵ�](https://github.com/apache/incubator-servicecomb-service-center/tree/master/scripts/release)��
 
-5. Last Step will make the releases in root folder.
+5. ��һ�������ڸ�Ŀ¼�����ɷ��а���
 
-6. Run the releases of frontend and service-center in both linux and windows.
+6. ��Linux��Windows����������ǰ����service-center��
 
-7. Run the [integration 
test](https://github.com/apache/incubator-servicecomb-service-center/tree/master/integration)
 on the release.
+7. 
����[���ɲ���](https://github.com/apache/incubator-servicecomb-service-center/tree/master/integration)��
 
-8. If all the test passes then send the release candidate to peers to test in 
different machines.
+8. �������ȫ�����Զ�ͨ���ˣ������а��ַ���ͬ���ڲ�ͬ�����Ͻ�����֤��
 
-9. Push the tag to master.
+9. ����ǩ���͵����ֿ⡣
 
-***Sign the Release***
+***�����а�ǩ��***
 
-10. Once the tag is pushed then using the tag download the source code from 
git [tag](https://github.com/apache/incubator-servicecomb-service-center/tags).
+10. 
��Github����Ҫ���а汾[��ǩ](https://github.com/apache/incubator-servicecomb-service-center/tags)��Դ�����
 
-11. Sign the 3 releases(linux, windows, src) and checksum.
+11. ����Linux���а���Windows���а���Դ�����ǩ����У��͡�
 
-12. Upload the release to dev/incubator/servicecomb Apache Svn.
+12. 
�ϴ����а浽[Apache���п����ֿ�](https://dist.apache.org/repos/dist/dev/incubator/servicecomb/incubator-servicecomb-service-center/).
 
-13. Download all the releases from SVN and verify the signature and checksum.
+13. ��SVN���ط��а�����֤ǩ����У�顣
 
-***PPMC Approval***
+***PPMC��׼***
 
-14. Send the voting mail in ***dev@servicecomb.apache.org*** for PPMC approval.
+14. ����ͶƱ�ʼ��� ***dev@servicecomb.apache.org***�� ����PPMC��׼.
 
-15. 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***.
+15. �ȴ�72Сʱ�����߻��3Ʊ+1����û��-1�������-1Ʊ���������Ⲣ��***��1��***���¿�ʼ��
 
-16. Publish the result of the vote in dev@servicecomb.apache.org.
+16. ��ͶƱ���������dev@servicecomb.apache.org��
 
-***IPMC approval***
+***IPMC��׼***
 
-17. Send the voting mail in ***gene...@incubator.apache.org*** for IPMC 
approval.
+17. ����ͶƱ�ʼ���***gene...@incubator.apache.org***������IPMC��׼��
 
-18. 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***
+18. �ȴ�72Сʱ�����߻��3Ʊ+1����û��-1�������-1Ʊ���������Ⲣ��***��1��***���¿�ʼ��
 
-19. Publish the result of the vote in gene...@incubator.apache.org.
+19. ��ͶƱ���������gene...@incubator.apache.org��
 
-***Announcements***
+***ͨ��***
 
-20. Upload the releases to release/incubator/servicecomb Apache Svn.
+20. 
�ϴ����а���[Apache���вֿ�](https://dist.apache.org/repos/dist/release/incubator/servicecomb/incubator-servicecomb-service-center/)��
 
-21. Wait for 24 hours to replicate the release in all the mirrors.
+21. �ȴ�24Сʱ�������о���ͬ����
 
-22. Upload the release page of ServiceComb Website.
+22. �ϴ�����ҳ����ServiceComb��վ��
 
-23. Send the announcement mails to dev@servicecomb.apache.org, 
gene...@incubator.apache.org, annou...@apache.org
+23. ���ͷ���ͨ���ʼ���dev@servicecomb.apache.org�� gene...@incubator.apache.org�� 
annou...@apache.org��
 
 
 
 
-## 发布Java-Chassis 需要做的步骤
+## ����Java-Chassis
 
-***版本制作以及验证版本***
+***׼����У�鷢�а�***
 
-1. Clone the java-chassis code.
+1. ��¡java-chassis���롣
 ```
 git clone g...@github.com:apache/incubator-servicecomb-java-chassis.git
 ```
 
-2. Cut the release using per command to replace all the versions in pom.xml 
files
+2. ʹ������perl����滻����pom.xml�ļ��еİ汾�Ų��ύ�Ķ������ء�
+```
+find . -name 'pom.xml'|xargs perl -pi -e 's/1.0.0-m2-SNAPSHOT/1.0.0-m2/g'
+```
 
-3. Create a Tag from the master branch using the version number.
+3. ��master��֧�ϴ���׼�������汾�ı�ǩ��
 
-4. Clear all the redundant servicecomb releases in repository.apache.org
+4. ����repository.apache.org����������ķ��а档
 
-5. Add the keys in a reference folder.
+5. ��GPG��Կ�ļ��������ļ��б��á�
 
-6. Update the key path and passphrase in .travis.settings file.
+6. ����`~/.m2/settings.xml`�ļ��е�GPG��Կ�ļ�·��������.
 
-7. Update the apache account username and password in the travis file.
+7. ����������Apache�ʻ��û��������롣
 
-8. Run the maven deploy command.
+8. �����������
 ```
-mvn deploy -DskipTests -Prelease -Pdistribution -Ppassphrase --settings 
.travis.settings.xml
+mvn deploy -DskipTests -Prelease -Pdistribution -Ppassphrase
 ```
 
-9. Once every thing is uploaded then use the staging repo to verify the build 
using Company workshop.
+9. ��������ִ�гɹ������е�jar�����ɹ��ϴ�����ʱ�ֿ������Company 
Workshop�������Ĺ�����֤��
 
-10. Share the staging repo with peers to verify on different OS and machines 
using the demo.
+10. ����ʱ�ֿ⹲������ˣ��ڲ�ͬ�Ļ����ͻ����Ͻ�����֤��
 
-11. If everything is fine then push the tag to master.
+11. �����֤ȫ��ͨ��������ǩ�ύ�����ֿ⡣
 
-12. Close the staging repo is apache repositories
+12. ����Apache��ʱ�ֿ⡣
 
-***Sign the Releases***
+***�����а�ǩ��***
 
-13. Download the source code and distribution from the staging repo.
+13. ����ʱ�ֿ����ض����ư���Դ�����
 
-14. Sign the 2 releases(distribution, src) and checksum.
+14. ���ɶ����ư���Դ�����ǩ����У��͡�
 
-15. Upload the release to dev/incubator/servicecomb Apache Svn.
+15. 
�ϴ����а���[Apache���п����ֿ�](https://dist.apache.org/repos/dist/dev/incubator/servicecomb/incubator-servicecomb-java-chassis/).
+.
 
-16. Download all the releases from SVN and verify the signature and checksum.
+16. ��SVN���ط��а�����֤ǩ����У�顣
 
-***PPMC approval***
+***PPMC��׼***
 
-17. Send the voting mail in dev@servicecomb.apache.org for PPMC approval.
+17. ����ͶƱ�ʼ��� ***dev@servicecomb.apache.org***�� ����PPMC��׼.
 
-18. 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.
+18. �ȴ�72Сʱ�����߻��3Ʊ+1����û��-1�������-1Ʊ���������Ⲣ��***��1��***���¿�ʼ��
 
-19. Publish the result of the vote in dev@servicecomb.apache.org.
+19. ��ͶƱ���������dev@servicecomb.apache.org��
 
-***IPMC approval***
+***IPMC��׼***
 
-20. Send the voting mail in gene...@incubator.apache.org
+20. ����ͶƱ�ʼ���***gene...@incubator.apache.org***������IPMC��׼��
 
-21. 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.
+21. �ȴ�72Сʱ�����߻��3Ʊ+1����û��-1�������-1Ʊ���������Ⲣ��***��1��***���¿�ʼ��
 
-22. Publish the result of the vote in gene...@incubator.apache.org.
+22. ��ͶƱ���������gene...@incubator.apache.org��
 
-***Announcements***
+***ͨ��***
 
-23. Upload the releases to release/incubator/servicecomb Apache Svn.
+23. 
�ϴ����а���[Apache���вֿ�](https://dist.apache.org/repos/dist/release/incubator/servicecomb/incubator-servicecomb-java-chassis/)��
 
-24. Wait for 24 hours to replicate the release in all the mirrors.
+24. �ȴ�24Сʱ�������о���ͬ����
 
-25. Upload the release page of ServiceComb Website.
+25. �ϴ�����ҳ����ServiceComb��վ��
 
-26. Send the announcement mails to dev@servicecomb.apache.org, 
gene...@incubator.apache.org, annou...@apache.org
+26. ���ͷ���ͨ���ʼ���dev@servicecomb.apache.org�� gene...@incubator.apache.org�� 
annou...@apache.org��
 
 
 
 
-## 发布Saga 需要做的步骤
+## ����Saga
 
-***版本制作以及验证版本***
+***׼����У�鷢�а�***
 
-1. Clone the saga code.
+1. ��¡Saga���롣
 ```
 g...@github.com:apache/incubator-servicecomb-saga.git
 ```
 
-2. Cut the release using per command to replace all the versions in pom.xml 
files
+2. ʹ������perl����滻����pom.xml�ļ��еİ汾�Ų��ύ�Ķ������ء�
+```
+find . -name 'pom.xml'|xargs perl -pi -e 's/1.0.0-m2-SNAPSHOT/1.0.0-m2/g'
+```
 
-3. Create a Tag from the master branch using the version number.
+3. ��master��֧�ϴ���׼�������汾�ı�ǩ��
 
-4. Clear all the redundant servicecomb releases in repository.apache.org
+4. ����repository.apache.org����������ķ��а档
 
-5. Add the keys in a reference folder.
+5. ��GPG��Կ�ļ��������ļ��б��á�
 
-6. Update the key path and passphrase in .travis.settings file.
+6. ����`~/.m2/settings.xml`�ļ��е�GPG��Կ�ļ�·��������.
 
-7. Update the apache account username and password in the travis file.
+7. ����������Apache�ʻ��û��������롣
 
-8. Run the maven deploy command.
+8. �����������
 ```
-mvn deploy -DskipTests --settings .travis.settings.xml -Ppassphrase -Prelease
+mvn deploy -DskipTests -Prelease -Pdistribution -Ppassphrase
 ```
 
-9. Once every thing is uploaded then use the staging repo to verify the build 
using Company workshop.
+9. ��������ִ�гɹ������е�jar�����ɹ��ϴ�����ʱ�ֿ�������ż���������֤�������ܡ�
 
-10. Share the staging repo with peers to verify on different OS and machines 
using the demo.
+10. ����ʱ�ֿ⹲������ˣ��ڲ�ͬ�Ļ����ͻ����Ͻ�����֤��
 
-11. If everything is fine then push the tag to master.
+11. �����֤ȫ��ͨ��������ǩ�ύ�����ֿ⡣
 
-12. Close the staging repo is apache repositories.
+12. ����Apache��ʱ�ֿ⡣
 
-***Sign the Releases***
+***�����а�ǩ��***
 
-13. Download the source code and distribution from the staging repo.
+13. ����ʱ�ֿ����ض����ư���Դ�����
 
-14. Sign the 2 releases(distribution, src) and checksum.
+14. ���ɶ����ư���Դ�����ǩ����У��͡�
 
-15. Upload the release to dev/incubator/servicecomb Apache Svn.
+15. 
�ϴ����а���[Apache���п����ֿ�](https://dist.apache.org/repos/dist/dev/incubator/servicecomb/incubator-servicecomb-java-chassis/).
+.
 
-16. Download all the releases from SVN and verify the signature and checksum.
+16. ��SVN���ط��а�����֤ǩ����У�顣
 
-***PPMC approval***
+***PPMC��׼***
 
-17. Send the voting mail in dev@servicecomb.apache.org.
+17. ����ͶƱ�ʼ��� ***dev@servicecomb.apache.org***�� ����PPMC��׼.
 
-18. 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.
+18. �ȴ�72Сʱ�����߻��3Ʊ+1����û��-1�������-1Ʊ���������Ⲣ��***��1��***���¿�ʼ��
 
-19. Publish the result of the vote in dev@servicecomb.apache.org.
+19. ��ͶƱ���������dev@servicecomb.apache.org��
 
-***IPMC approval***
+***IPMC��׼***
 
-20. Send the voting mail in gene...@incubator.apache.org
+20. ����ͶƱ�ʼ���***gene...@incubator.apache.org***������IPMC��׼��
 
-21. 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.
+21. �ȴ�72Сʱ�����߻��3Ʊ+1����û��-1�������-1Ʊ���������Ⲣ��***��1��***���¿�ʼ��
 
-22. Publish the result of the vote in gene...@incubator.apache.org.
+22. ��ͶƱ���������gene...@incubator.apache.org��
 
-***Announcements***
+***ͨ��***
 
-23. Upload the releases to release/incubator/servicecomb Apache Svn.
+23. 
�ϴ����а���[Apache���вֿ�](https://dist.apache.org/repos/dist/release/incubator/servicecomb/incubator-servicecomb-saga/)��
 
-24. Wait for 24 hours to replicate the release in all the mirrors.
+24. �ȴ�24Сʱ�������о���ͬ����
 
-25. Upload the release page of ServiceComb Website.
+25. �ϴ�����ҳ����ServiceComb��վ��
 
-26. Send the announcement mails to dev@servicecomb.apache.org, 
gene...@incubator.apache.org, annou...@apache.org
+26. ���ͷ���ͨ���ʼ���dev@servicecomb.apache.org�� gene...@incubator.apache.org�� 
annou...@apache.org��
 
 
-**NOTE**
-The whole process generally takes 2 weeks to complete assuming you don't get 
any -1 from PPMC and IMPC, so please plan the release activity before hand.
+**ע��**
+�������й���ͨ����Ҫ2��ʱ�䣬���PPMCͶƱ��IPMCȫ����һ����ͨ�����������ǰ׼�����л��
diff --git a/_developers/release_guide.md b/_developers/release_guide.md
index 36c2cd6..78007f3 100644
--- a/_developers/release_guide.md
+++ b/_developers/release_guide.md
@@ -247,7 +247,7 @@ find . -name 'pom.xml'|xargs perl -pi -e 
's/1.0.0-m2-SNAPSHOT/1.0.0-m2/g'
 mvn deploy -DskipTests -Ppassphrase -Prelease
 ```
 
-9. Once every thing is uploaded then use the staging repo to verify the build 
using Company workshop.
+9. Once every thing is uploaded then use the staging repo to verify the build 
using the acceptance test.
 
 10. Share the staging repo with peers to verify on different OS and machines 
using the demo.
 


 

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Reply via email to