You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tvm.apache.org by li...@apache.org on 2020/06/28 08:24:52 UTC

[incubator-tvm] branch master updated: [Doc] minor fix for release doc (#5948)

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

liuyizhi pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-tvm.git


The following commit(s) were added to refs/heads/master by this push:
     new bdc5547  [Doc] minor fix for release doc (#5948)
bdc5547 is described below

commit bdc55470d503f8dfa1cb992a7e19164e111794a3
Author: Yizhi Liu <li...@apache.org>
AuthorDate: Sun Jun 28 01:24:38 2020 -0700

    [Doc] minor fix for release doc (#5948)
---
 docs/contribute/release_process.rst | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/docs/contribute/release_process.rst b/docs/contribute/release_process.rst
index ceead3d..9fca35a 100644
--- a/docs/contribute/release_process.rst
+++ b/docs/contribute/release_process.rst
@@ -17,8 +17,8 @@
 
 .. _release_process:
 
-Apache TVM (incubator) Release Process
-======================================
+Apache TVM (incubating) Release Process
+=======================================
 
 The release manager role in TVM means you are responsible for a few different things:
 
@@ -57,7 +57,7 @@ You can skip this section if you have already uploaded your key.
 
 After generating the gpg key, you need to upload your key to a public key server. Please refer to https://www.apache.org/dev/openpgp.html#generate-key for details.
 
-If you want to do the release on another machine, you can transfer your gpg key to that machine via the gpg --export and gpg --import commands.
+If you want to do the release on another machine, you can transfer your gpg key to that machine via the :code:`gpg --export` and :code:`gpg --import` commands.
 
 The last step is to update the KEYS file with your code signing key https://www.apache.org/dev/openpgp.html#export-public-key. Check in the changes to the master branch.
 
@@ -80,6 +80,7 @@ Go to the GitHub repositories "releases" tab and click "Draft a new release",
 - Select the commit by clicking Target: branch > Recent commits > $commit_hash 
 - Copy and paste release note draft into the description box
 - Select "This is a pre-release"
+- Click "Publish release"
 
 Notice that one can still apply changes to the BRANCH after the cut, while the TAG is fixed. If any change is required for this release, a new TAG has to be created.
 
@@ -94,11 +95,13 @@ Create source code artifacts,
 .. code-block:: bash
 
 	git clone git@github.com:apache/incubator-tvm.git apache-tvm-src-v0.6.0.rc0-incubating
+	cd apache-tvm-src-v0.6.0.rc0-incubating
 	git checkout v0.6
 	git submodule update --init --recursive
 	git checkout v0.6.0.rc0
 	rm -rf .DS_Store
 	find . -name ".git*" -print0 | xargs -0 rm -rf
+	cd ..
 	brew install gnu-tar 
 	gtar -czvf apache-tvm-src-v0.6.0.rc0-incubating.tar.gz apache-tvm-src-v0.6.0.rc0-incubating