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 2018/10/04 04:12:35 UTC
[beam-site] branch mergebot updated (021f266 -> 4091c5d)
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 021f266 This closes #570
add 5122163 Prepare repository for deployment.
new 02d574a Update release guide
new ad9b65d Edit suggestions
new 4091c5d This closes #572
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:
.../2018/10/03/beam-2.7.0.html} | 81 +++++++---
content/blog/index.html | 32 ++++
content/feed.xml | 174 ++++++++++-----------
content/get-started/downloads/index.html | 2 +
content/index.html | 10 +-
src/contribute/release-guide.md | 5 +-
6 files changed, 188 insertions(+), 116 deletions(-)
copy content/{beam/capability/2016/04/03/presentation-materials.html => blog/2018/10/03/beam-2.7.0.html} (78%)
[beam-site] 01/03: Update release guide
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 02d574ab0ec1a1191a53b6c1b7d87da0f6cbdf1d
Author: Ahmet Altay <al...@google.com>
AuthorDate: Wed Oct 3 16:50:45 2018 -0700
Update release guide
---
src/contribute/release-guide.md | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/src/contribute/release-guide.md b/src/contribute/release-guide.md
index cddad39..b8cd62c 100644
--- a/src/contribute/release-guide.md
+++ b/src/contribute/release-guide.md
@@ -181,7 +181,8 @@ When contributors resolve an issue in JIRA, they are tagging it with a release t
__Attention__: Only PMC has permission to perform this. If you are not a PMC, please ask for help in dev@ mailing list.
1. In JIRA, navigate to the [`Beam > Administration > Versions`](https://issues.apache.org/jira/plugins/servlet/project-config/BEAM/versions).
-1. Add a new release: choose the next minor version number compared to the one currently underway, select today’s date as the `Start Date`, and choose `Add`.
+1. Add a new release: choose the next minor version number compared to the one currently underway, select release cut date (today’s date) as the `Start Date`, and choose `Add`.
+1. At the end of the release, in the same page mark the recently released version as released. (Use the `...` menu and choose `Release`).
### Triage release-blocking issues in JIRA
[beam-site] 03/03: This closes #572
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 4091c5d00e0c48c0bdb9f6dc71d421ddd4085fd4
Merge: 5122163 ad9b65d
Author: Mergebot <me...@apache.org>
AuthorDate: Thu Oct 4 04:11:38 2018 +0000
This closes #572
src/contribute/release-guide.md | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
[beam-site] 02/03: Edit suggestions
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 ad9b65dbfdb0c98c4f381b05ede31416a5f7f95b
Author: Melissa Pashniak <me...@google.com>
AuthorDate: Wed Oct 3 18:37:20 2018 -0700
Edit suggestions
---
src/contribute/release-guide.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/src/contribute/release-guide.md b/src/contribute/release-guide.md
index b8cd62c..6a5e1c4 100644
--- a/src/contribute/release-guide.md
+++ b/src/contribute/release-guide.md
@@ -180,9 +180,9 @@ When contributors resolve an issue in JIRA, they are tagging it with a release t
__Attention__: Only PMC has permission to perform this. If you are not a PMC, please ask for help in dev@ mailing list.
-1. In JIRA, navigate to the [`Beam > Administration > Versions`](https://issues.apache.org/jira/plugins/servlet/project-config/BEAM/versions).
-1. Add a new release: choose the next minor version number compared to the one currently underway, select release cut date (today’s date) as the `Start Date`, and choose `Add`.
-1. At the end of the release, in the same page mark the recently released version as released. (Use the `...` menu and choose `Release`).
+1. In JIRA, navigate to [`Beam > Administration > Versions`](https://issues.apache.org/jira/plugins/servlet/project-config/BEAM/versions).
+1. Add a new release. Choose the next minor version number after the version currently underway, select the release cut date (today’s date) as the `Start Date`, and choose `Add`.
+1. At the end of the release, go to the same page and mark the recently released version as released. Use the `...` menu and choose `Release`.
### Triage release-blocking issues in JIRA