You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by me...@apache.org on 2017/12/14 18:35:59 UTC

[beam-site] branch mergebot updated (8534d0e -> 7ba9a65)

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

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


    from 8534d0e  This closes #363
     add bc530c0  Prepare repository for deployment.
     new a35a365  Move reporter.apache.org step to finalize section
     new b6ac0cb  Expand instructions for pushing release version tag
     new 7ba9a65  This closes #365

The 3 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 content/contribute/work-in-progress/index.html |  6 ------
 content/documentation/dsls/sql/index.html      |  6 +-----
 src/contribute/release-guide.md                | 19 +++++++++++--------
 3 files changed, 12 insertions(+), 19 deletions(-)

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

[beam-site] 01/03: Move reporter.apache.org step to finalize section

Posted by 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 a35a3656e904343d17cbf919e7e7202d12cc18da
Author: Kenneth Knowles <kl...@google.com>
AuthorDate: Thu Dec 14 08:31:47 2017 -0800

    Move reporter.apache.org step to finalize section
---
 src/contribute/release-guide.md | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/src/contribute/release-guide.md b/src/contribute/release-guide.md
index bbf19df..bb9e028 100644
--- a/src/contribute/release-guide.md
+++ b/src/contribute/release-guide.md
@@ -465,6 +465,10 @@ Merge the website pull request to [list the release]({{ site.baseurl }}/get-star
 
 In JIRA, inside [version management](https://issues.apache.org/jira/plugins/servlet/project-config/BEAM/versions), hover over the current release and a settings menu will appear. Click `Release`, and select today’s date.
 
+### Recordkeeping with ASF
+
+Use reporter.apache.org to seed the information about the release into future project reports.
+
 ### Checklist to proceed to the next step
 
 * Maven artifacts released and indexed in the [Maven Central Repository](https://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.apache.beam%22)
@@ -473,6 +477,7 @@ In JIRA, inside [version management](https://issues.apache.org/jira/plugins/serv
 * Website pull request to [list the release]({{ site.baseurl }}/get-started/downloads/) and publish the [API reference manual]({{ site.baseurl }}/documentation/sdks/javadoc/) merged
 * Release tagged in the source code repository
 * Release version finalized in JIRA. (Note: Not all committers have administrator access to JIRA. If you end up getting permissions errors ask on the mailing list for assistance.)
+* Release version is listed at reporter.apache.org
 
 **********
 
@@ -488,10 +493,6 @@ Announce on the release on the user@ mailing list, listing major improvements an
 
 Announce the release on the announce@apache.org mailing list.
 
-### Recordkeeping
-
-Use reporter.apache.org to seed the information about the release into future project reports.
-
 ### Beam blog
 
 Major or otherwise important releases should have a blog post. Write one if needed for this particular release. Minor releases that don’t introduce new major functionality don’t necessarily need to be blogged.

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

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

Posted by 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>.

[beam-site] 03/03: This closes #365

Posted by 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 7ba9a650ac0efac5de342e71943d7b676a84b46f
Merge: bc530c0 b6ac0cb
Author: Mergebot <me...@apache.org>
AuthorDate: Thu Dec 14 18:34:10 2017 +0000

    This closes #365

 src/contribute/release-guide.md | 19 +++++++++++--------
 1 file changed, 11 insertions(+), 8 deletions(-)

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