[beam-site] 02/03: Expand instructions for pushing release version tag

[me...@apache.org]

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

mergebot-role pushed a commit to branch mergebot
in repository https://gitbox.apache.org/repos/asf/beam-site.git

commit b6ac0cbed0968ad19c6a730f9a660bbbbd247800
Author: Kenneth Knowles <kl...@google.com>
AuthorDate: Thu Dec 14 08:35:32 2017 -0800

    Expand instructions for pushing release version tag
---
 src/contribute/release-guide.md | 10 ++++++----
 1 file changed, 6 insertions(+), 4 deletions(-)

diff --git a/src/contribute/release-guide.md b/src/contribute/release-guide.md
index bb9e028..b09ff0b 100644
--- a/src/contribute/release-guide.md
+++ b/src/contribute/release-guide.md
@@ -252,14 +252,14 @@ The core of the release process is the build-vote-fix cycle. Each cycle produces
 Set up a few environment variables to simplify Maven commands that follow. This identifies the release candidate being built. Start with `RC_NUM` equal to `1` and increment it for each candidate.
 
     RC_NUM="1"
-    TAG="v${VERSION}-RC${RC_NUM}"
+    RC_TAG="v${VERSION}-RC${RC_NUM}"
 
 Use Maven release plugin to build the release artifacts, as follows:
 
     mvn release:prepare \
         -Dresume=false \
         -DreleaseVersion=${VERSION} \
-        -Dtag=${TAG} \
+        -Dtag=${RC_TAG} \
         -DupdateWorkingCopyVersions=false
 
 Use Maven release plugin to stage these artifacts on the Apache Nexus repository, as follows:
@@ -453,9 +453,11 @@ Copy the source release from the `dev` repository to the `release` repository at
 
 ### Git tag
 
-Create a new Git tag for the released version by copying the tag for the final release candidate, as follows:
+Create and push a new signed tag for the released version by copying the tag for the final release candidate, as follows:
 
-    git tag -s “v${VERSION}” ${TAG}
+    VERSION_TAG="v${VERSION}"
+    git tag -s "$VERSION_TAG" "$RC_TAG"
+    git push github "$VERSION_TAG"
 
 ### Merge website pull request
 

-- 
To stop receiving notification emails like this one, please contact
"commits@beam.apache.org" <co...@beam.apache.org>.