diff --git a/community/how-to-release.md b/community/how-to-release.md index 87f95d73deb..95736447f4f 100644 --- a/community/how-to-release.md +++ b/community/how-to-release.md @@ -477,16 +477,16 @@ Hello Linkis Community, This is a call for vote to release Apache Linkis version ${release_version}-${rc_version}. Release notes: - https://github.com/apache/linkis/releases/tag/v${release_version}-${rc_version} - + https://linkis.apache.org/download/release-notes-${release_version} + The release candidates: https://dist.apache.org/repos/dist/dev/linkis/${release_version}-${rc_version}/ - Maven artifacts are available in a staging repository at: + Maven artifacts are available in a staging repository at: https://repository.apache.org/content/repositories/orgapachelinkis-{staging-id} - - Git tag for the release: - https://github.com/apache/linkis/tree/v${release_version}-${rc_version} + + Git branch for the release: + https://github.com/apache/linkis/tree/${release_version}-${rc_version} Keys to verify the Release Candidate: https://downloads.apache.org/linkis/KEYS @@ -510,7 +510,10 @@ Hello Linkis Community, [] LICENSE and NOTICE files are correct for each Linkis repo. [] All files have license headers if necessary. [] No unlicensed compiled archives bundled in source archive. - + + Steps to validate the release,Please refer to: + https://linkis.apache.org/community/how-to-verify + Thanks, ${Linkis Release Manager} ``` @@ -572,7 +575,7 @@ Move source and binary packages from svn's `dev` directory to the `release` dire ```shell #Mobile source package and binary package -$ svn mv https://dist.apache.org/repos/dist/dev/linkis/${release_version}-${rc_version} https://dist.apache.org/repos/dist/release/ linkis/ -m "transfer packages for ${release_version}-${rc_version}" +$ svn mv https://dist.apache.org/repos/dist/dev/linkis/${release_version}-${rc_version} https://dist.apache.org/repos/dist/release/linkis/${release_version} -m "transfer packages for ${release_version}-${rc_version}" # The following operations decide whether to update the key of the release branch according to the actual situation # Clear the KEYS in the original release directory diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-release.md b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-release.md index 81436685887..6562d396de4 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-release.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-release.md @@ -512,7 +512,7 @@ $ cd dist/linkis_svn_dev/ $ svn status # 添加到svn版本 $ svn add 1.1.2-RC1 -$ status +$ svn status #提交至svn远程服务器 $ svn commit -m "prepare for 1.1.2-RC1" @@ -670,9 +670,9 @@ Hello Apache Linkis PMC and Community, The vote closes now. The vote PASSES with xx (+1 binding) votes from the PMC members, - member one - member two - member three + - member one + - member two + - member three ... xx (+1 non-binding) votes from the rest of the developer community,