This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/beam.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 4760ec3 Publishing website 2019/09/20 01:10:50 at commit ec3e770
4760ec3 is described below
commit 4760ec39e2bf818a8cac94126076e0057f13eff4
Author: jenkins <bui...@apache.org>
AuthorDate: Fri Sep 20 01:10:50 2019 +0000
Publishing website 2019/09/20 01:10:50 at commit ec3e770
---
website/generated-content/contribute/release-guide/index.html | 2 ++
1 file changed, 2 insertions(+)
diff --git a/website/generated-content/contribute/release-guide/index.html
b/website/generated-content/contribute/release-guide/index.html
index 9385dad..40403b8 100644
--- a/website/generated-content/contribute/release-guide/index.html
+++ b/website/generated-content/contribute/release-guide/index.html
@@ -996,6 +996,8 @@ to find environment issues this way without having to wait
until the full build
<p>The list of release-blocking issues is available at the <a
href="https://issues.apache.org/jira/browse/BEAM/?selectedTab=com.atlassian.jira.jira-projects-plugin:versions-panel";>version
status page</a>. Triage each unresolved issue with one of the following
resolutions:</p>
+<p>The release manager should triage what does and does not block a release.
An issue should not block the release if the problem exists in the current
released version or is a bug in new functionality that does not exist in the
current released version. It should be a blocker if the bug is a regression
between the currently released version and the release in progress and has no
easy workaround.</p>
+
<p>For all JIRA issues:</p>
<ul>
