You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@kyuubi.apache.org by ya...@apache.org on 2021/08/18 04:07:44 UTC

[incubator-kyuubi] branch branch-1.3 updated: [KYUUBI #945] [DOCS] Update release guide

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

yao pushed a commit to branch branch-1.3
in repository https://gitbox.apache.org/repos/asf/incubator-kyuubi.git


The following commit(s) were added to refs/heads/branch-1.3 by this push:
     new 95fb96e  [KYUUBI #945] [DOCS] Update release guide
95fb96e is described below

commit 95fb96ecedce06378439104012d94d930067381a
Author: Cheng Pan <ch...@apache.org>
AuthorDate: Wed Aug 18 10:27:14 2021 +0800

    [KYUUBI #945] [DOCS] Update release guide
    
    <!--
    Thanks for sending a pull request!
    
    Here are some tips for you:
      1. If this is your first time, please read our contributor guidelines: https://kyuubi.readthedocs.io/en/latest/community/contributions.html
      2. If the PR is related to an issue in https://github.com/apache/incubator-kyuubi/issues, add '[KYUUBI #XXXX]' in your PR title, e.g., '[KYUUBI #XXXX] Your PR title ...'.
      3. If the PR is unfinished, add '[WIP]' in your PR title, e.g., '[WIP][KYUUBI #XXXX] Your PR title ...'.
    -->
    
    ### _Why are the changes needed?_
    <!--
    Please clarify why the changes are needed. For instance,
      1. If you add a feature, you can talk about the use case of it.
      2. If you fix a bug, you can clarify why it is a bug.
    -->
    
    ### _How was this patch tested?_
    - [ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible
    
    - [ ] Add screenshots for manual tests if appropriate
    
    - [ ] [Run test](https://kyuubi.readthedocs.io/en/latest/develop_tools/testing.html#running-tests) locally before make a pull request
    
    Closes #945 from pan3793/doc.
    
    Closes #945
    
    a46af55e [Cheng Pan] [DOCS] Update release guide
    
    Authored-by: Cheng Pan <ch...@apache.org>
    Signed-off-by: Kent Yao <ya...@apache.org>
    (cherry picked from commit 65e579271bc3c44d4895080571a2a8c6f1ad77c2)
    Signed-off-by: Kent Yao <ya...@apache.org>
---
 docs/community/release.md | 18 ++++++++++++++----
 1 file changed, 14 insertions(+), 4 deletions(-)

diff --git a/docs/community/release.md b/docs/community/release.md
index 4c9f48f..f2e8553 100644
--- a/docs/community/release.md
+++ b/docs/community/release.md
@@ -93,13 +93,19 @@ pub   ed25519/ED4E2E5B 2021-07-02 [SC]
 uid         [ultimate] Cheng Pan <ch...@apache.org>
 sub   cv25519/C7207C04 2021-07-02 [E]
 ```
-Here, the key ID is the 8-digit hex string in the pub line: ED4E2E5B.
+Here, the key ID is the 8-digit hex string in the pub line: `ED4E2E5B`.
+
+To export the PGP public key, using:
+```shell
+gpg --armor --export ED4E2E5B
+```
 
 The last step is to update the KEYS file with your code signing key 
 https://www.apache.org/dev/openpgp.html#export-public-key
 
 ```shell
-svn checkout --depth=files "https://dist.apache.org/repos/dist/dev/incubator/kyuubi" svn-kyuubi
+svn checkout --depth=files "https://dist.apache.org/repos/dist/dev/incubator/kyuubi" work/svn-kyuubi
+cd work/svn-kyuubi
 ... edit svn-kyuubi/KEYS file
 svn commit --username "${ASF_USERNAME}" --password "${ASF_PASSWORD}" --message "Update KEYS"
 ```
@@ -144,7 +150,7 @@ The tag pattern is `v${RELEASE_VERSION}-rc${RELEASE_RC_NO}`, e.g. `v1.3.0-incuba
 staging Maven repo.
 
 ```shell
-build/release/releas.sh publish
+build/release/release.sh publish
 ```
 
 ## Vote on the release candidate
@@ -173,7 +179,7 @@ Move the sub-directory in "dev" to the corresponding directory in "release". If
 KEYS file, also update the release copy.
 
 ```shell
-build/release/releas.sh finalize
+build/release/release.sh finalize
 ```
 
 Verify that the resources are present in https://www.apache.org/dist/incubator/kyuubi/. It may take a while for them
@@ -187,6 +193,10 @@ After some time this will be sync’d to [Maven Central](https://search.maven.or
 
 ## Promote the release
 
+## Update Website
+
+TODO
+
 ### Create an Announcement
 
 Once everything is working create an announcement on the website and then send an e-mail to the mailing list.