This is an automated email from the ASF dual-hosted git repository. ningjiang pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/servicecomb-website.git
commit 7e46bd97a652a2e2cbaab8770c07a72adf32592c Author: asifdxtreme <[email protected]> AuthorDate: Fri Nov 30 18:45:01 2018 +0530 Update the Release Guide --- _developers/cn/release_guide.md | 66 +++++++++++++++------------------------ _developers/release_guide.md | 69 +++++++++++++++-------------------------- 2 files changed, 50 insertions(+), 85 deletions(-) diff --git a/_developers/cn/release_guide.md b/_developers/cn/release_guide.md index 7f6508e..eb57c4f 100755 --- a/_developers/cn/release_guide.md +++ b/_developers/cn/release_guide.md @@ -110,35 +110,30 @@ gvt restore 11. 生成Linux发行包，Windows发行包和源码包的签名和校验和。 -12. 上传发行版到[Apache发行开发仓库](https://dist.apache.org/repos/dist/dev/incubator/servicecomb/incubator-servicecomb-service-center/). +12. 上传发行版到[Apache发行开发仓库](https://dist.apache.org/repos/dist/dev/servicecomb/servicecomb-service-center/). 13. 从SVN下载发行包，验证签名和校验。 -***PPMC批准*** +***PMC批准*** -14. 发送投票邮件至 ***[email protected]***， 发起PPMC批准. +14. 发送投票邮件至 ***[email protected]***， 发起PMC批准. 15. 等待72小时，或者获得3票+1并且没有-1。如果有-1票，修正问题并从***第1步***重新开始。 16. 将投票结果发布到[email protected]。 -***IPMC批准*** - -17. 发送投票邮件至***[email protected]***，发起IPMC批准。 - -18. 等待72小时，或者获得3票+1并且没有-1。如果有-1票，修正问题并从***第1步***重新开始。 - -19. 将投票结果发布到[email protected]。 ***通告*** -20. 上传发行包至[Apache发行仓库](https://dist.apache.org/repos/dist/release/incubator/servicecomb/incubator-servicecomb-service-center/)。 +20. 上传发行包至[Apache发行仓库](https://dist.apache.org/repos/dist/release/servicecomb/servicecomb-service-center/)。 21. 等待24小时，让所有镜像同步。 -22. 上传发行页面至ServiceComb网站。 +22. Delete old releases from [dev](https://dist.apache.org/repos/dist/dev) 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. -23. 发送发行通告邮件到[email protected]， [email protected]， [email protected]。 +23. 上传发行页面至ServiceComb网站。 + +24. 发送发行通告邮件到[email protected]， [email protected]。 @@ -186,36 +181,31 @@ mvn deploy -DskipTests -Prelease -Pdistribution -Ppassphrase 14. 生成二进制包和源码包的签名和校验和。 -15. 上传发行包到[Apache发行开发仓库](https://dist.apache.org/repos/dist/dev/incubator/servicecomb/incubator-servicecomb-java-chassis/). +15. 上传发行包到[Apache发行开发仓库](https://dist.apache.org/repos/dist/dev/servicecomb/servicecomb-java-chassis/). . 16. 从SVN下载发行包，验证签名和校验。 -***PPMC批准*** +***PMC批准*** -17. 发送投票邮件至 ***[email protected]***， 发起PPMC批准. +17. 发送投票邮件至 ***[email protected]***， 发起PMC批准. 18. 等待72小时，或者获得3票+1并且没有-1。如果有-1票，修正问题并从***第1步***重新开始。 19. 将投票结果发布到[email protected]。 -***IPMC批准*** - -20. 发送投票邮件至***[email protected]***，发起IPMC批准。 - -21. 等待72小时，或者获得3票+1并且没有-1。如果有-1票，修正问题并从***第1步***重新开始。 - -22. 将投票结果发布到[email protected]。 ***通告*** -23. 上传发行包至[Apache发行仓库](https://dist.apache.org/repos/dist/release/incubator/servicecomb/incubator-servicecomb-java-chassis/)。 +23. 上传发行包至[Apache发行仓库](https://dist.apache.org/repos/dist/release/servicecomb/servicecomb-java-chassis/)。 24. 等待24小时，让所有镜像同步。 -25. 上传发行页面至ServiceComb网站。 +25. Delete old releases from [dev](https://dist.apache.org/repos/dist/dev) 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. + +26. 上传发行页面至ServiceComb网站。 -26. 发送发行通告邮件到[email protected]， [email protected]， [email protected]。 +27. 发送发行通告邮件到[email protected]， [email protected]。 @@ -263,37 +253,31 @@ mvn deploy -DskipTests -Prelease -Pdistribution -Ppassphrase 14. 生成二进制包和源码包的签名和校验和。 -15. 上传发行包到[Apache发行开发仓库](https://dist.apache.org/repos/dist/dev/incubator/servicecomb/incubator-servicecomb-java-chassis/). +15. 上传发行包到[Apache发行开发仓库](https://dist.apache.org/repos/dist/dev/servicecomb/servicecomb-java-chassis/). . 16. 从SVN下载发行包，验证签名和校验。 -***PPMC批准*** +***PMC批准*** -17. 发送投票邮件至 ***[email protected]***， 发起PPMC批准. +17. 发送投票邮件至 ***[email protected]***， 发起PMC批准. 18. 等待72小时，或者获得3票+1并且没有-1。如果有-1票，修正问题并从***第1步***重新开始。 19. 将投票结果发布到[email protected]。 -***IPMC批准*** - -20. 发送投票邮件至***[email protected]***，发起IPMC批准。 - -21. 等待72小时，或者获得3票+1并且没有-1。如果有-1票，修正问题并从***第1步***重新开始。 - -22. 将投票结果发布到[email protected]。 - ***通告*** -23. 上传发行包至[Apache发行仓库](https://dist.apache.org/repos/dist/release/incubator/servicecomb/incubator-servicecomb-saga/)。 +23. 上传发行包至[Apache发行仓库](https://dist.apache.org/repos/dist/release/servicecomb/servicecomb-saga/)。 24. 等待24小时，让所有镜像同步。 -25. 上传发行页面至ServiceComb网站。 +25. Delete old releases from [dev](https://dist.apache.org/repos/dist/dev) 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. + +26. 上传发行页面至ServiceComb网站。 -26. 发送发行通告邮件到[email protected]， [email protected]， [email protected]。 +27. 发送发行通告邮件到[email protected]， [email protected]。 **注意** -整个发行过程通常需要2周时间，如果PPMC投票和IPMC全部都一次性通过。因此请提前准备发行活动。 +整个发行过程通常需要2周时间，如果PMC全部都一次性通过。因此请提前准备发行活动。 diff --git a/_developers/release_guide.md b/_developers/release_guide.md index 26db005..f029b22 100755 --- a/_developers/release_guide.md +++ b/_developers/release_guide.md @@ -107,39 +107,33 @@ gvt restore 1. Once the tag is pushed then using the tag download the source code from git [tag](https://github.com/apache/servicecomb-service-center/tags). -2. Sign the 3 releases(linux, windows, src) and checksum. +2. Sign the 4 releases(linux, windows, darwin, src) and checksum. -3. Create a new directory [Apache dev Release SVN](https://dist.apache.org/repos/dist/dev/incubator/servicecomb/incubator-servicecomb-service-center/) with release package name and release candidate number. (for example : if you want to release 1.0.0-m2 and this is the second attempt of the release then the folder structure will be `1.0.0-m2/rc02`) +3. Create a new directory [Apache dev Release SVN](https://dist.apache.org/repos/dist/dev/servicecomb/servicecomb-service-center/) with release package name and release candidate number. (for example : if you want to release 1.0.0-m2 and this is the second attempt of the release then the folder structure will be `1.0.0-m2/rc02`) 4. Upload the release to the directory created in last step. 5. Download all the releases from SVN and verify the signature and checksum. -***PPMC Approval*** +***PMC Approval*** -1. Send the voting mail in ***[email protected]*** for PPMC approval. +1. Send the voting mail in ***[email protected]*** for 1PMC approval. 2. 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***. 3. Publish the result of the vote in [email protected]. -***IPMC approval*** - -1. Send the voting mail in ***[email protected]*** for IPMC approval. - -2. 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*** - -3. Publish the result of the vote in [email protected]. - ***Announcements*** -1. Upload the releases to [Apache release repository](https://dist.apache.org/repos/dist/release/incubator/servicecomb/incubator-servicecomb-service-center/). +1. Upload the releases to [Apache release repository](https://dist.apache.org/repos/dist/release/servicecomb/servicecomb-service-center/). 2. Wait for 24 hours to replicate the release in all the mirrors. -3. Upload the release page of ServiceComb Website. +3. Delete old releases from [dev](https://dist.apache.org/repos/dist/dev) 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. + +4. Upload the release page of ServiceComb Website. -4. Send the announcement mails to [email protected], [email protected], [email protected] +5. Send the announcement mails to [email protected], [email protected] @@ -187,37 +181,31 @@ mvn deploy -DskipTests -Prelease -Pdistribution -Ppassphrase 2. Sign the 2 releases(distribution, src) and checksum. -3. Create a new directory [Apache dev Release SVN](https://dist.apache.org/repos/dist/dev/incubator/servicecomb/incubator-servicecomb-java-chassis/) 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 `1.0.0-m2/rc01`) +3. Create a new directory [Apache dev Release SVN](https://dist.apache.org/repos/dist/dev/servicecomb/servicecomb-java-chassis/) 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 `1.0.0-m2/rc01`) 4. Upload the release to directory created in last step. 5. Download all the releases from SVN and verify the signature and checksum. -***PPMC approval*** +***PMC approval*** -1. Send the voting mail in [email protected] for PPMC approval. +1. Send the voting mail in [email protected] for PMC approval. 2. 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. 3. Publish the result of the vote in [email protected]. -***IPMC approval*** - -1. Send the voting mail in [email protected] - -2. 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. - -3. Publish the result of the vote in [email protected]. - ***Announcements*** -1. Upload the releases to [Apache release repository](https://dist.apache.org/repos/dist/release/incubator/servicecomb/incubator-servicecomb-java-chassis/). +1. Upload the releases to [Apache release repository](https://dist.apache.org/repos/dist/release/servicecomb/servicecomb-java-chassis/). 2. Wait for 24 hours to replicate the release in all the mirrors. -3. Upload the release page of ServiceComb Website. +3. Delete old releases from [dev](https://dist.apache.org/repos/dist/dev) 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. + +4. Upload the release page of ServiceComb Website. -4. Send the announcement mails to [email protected], [email protected], [email protected] +5. Send the announcement mails to [email protected], [email protected] @@ -264,13 +252,13 @@ mvn deploy -DskipTests -Ppassphrase -Prelease 2. Sign the 2 releases(distribution, src) and checksum. -3. Create a new directory [Apache dev Release SVN](https://dist.apache.org/repos/dist/dev/incubator/servicecomb/incubator-servicecomb-saga/) with release package name and release candidate number. (for example : if you want to release 1.0.0-m2 and this is the third attempt of the release then the folder structure will be `1.0.0-m2/rc03`) +3. Create a new directory [Apache dev Release SVN](https://dist.apache.org/repos/dist/dev/servicecomb/servicecomb-saga/) with release package name and release candidate number. (for example : if you want to release 1.0.0-m2 and this is the third attempt of the release then the folder structure will be `1.0.0-m2/rc03`) 4. Upload the release to directory created in last step. 5. Download all the releases from SVN and verify the signature and checksum. -***PPMC approval*** +***PMC approval*** 1. Send the voting mail in [email protected]. @@ -278,25 +266,18 @@ mvn deploy -DskipTests -Ppassphrase -Prelease 3. Publish the result of the vote in [email protected]. -***IPMC approval*** - -1. Send the voting mail in [email protected] - -2. 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. - -3. Publish the result of the vote in [email protected]. - ***Announcements*** -1. Upload the releases to [Apache release repository](https://dist.apache.org/repos/dist/release/incubator/servicecomb/incubator-servicecomb-saga/). - +1. Upload the releases to [Apache release repository](https://dist.apache.org/repos/dist/release/servicecomb/servicecomb-saga/). 2. Wait for 24 hours to replicate the release in all the mirrors. -3. Upload the release page of ServiceComb Website. +3. Delete old releases from [dev](https://dist.apache.org/repos/dist/dev) 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. + +4. Upload the release page of ServiceComb Website. -4. Send the announcement mails to [email protected], [email protected], [email protected] +5. Send the announcement mails to [email protected], [email protected] **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. + - The whole process generally takes 1 weeks to complete assuming you don't get any -1 from PMC, so please plan the release activity before hand.
