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 d109061 Publishing website 2018/10/23 15:56:41 at commit f7b22d7
d109061 is described below
commit d1090615df5dd9bf432e0040badf6873130f8a43
Author: jenkins <[email protected]>
AuthorDate: Tue Oct 23 15:56:42 2018 +0000
Publishing website 2018/10/23 15:56:41 at commit f7b22d7
---
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 8039ae0..e3a60ce 100644
--- a/website/generated-content/contribute/release-guide/index.html
+++ b/website/generated-content/contribute/release-guide/index.html
@@ -602,6 +602,8 @@ Automation Reliability</a>.</p>
<li>If the issue has not been resolved and it is not acceptable to release
until it is fixed, the release cannot proceed. Instead, work with the Beam
community to resolve the issue.</li>
</ul>
+<p>If there is a bug found in the RC creation process/tools, those issues
should be considered high priority and fixed in 7 days.</p>
+
<h3 id="review-release-notes-in-jira">Review Release Notes in JIRA</h3>
<p>JIRA automatically generates Release Notes based on the <code
class="highlighter-rouge">Fix Version</code> field applied to issues. Release
Notes are intended for Beam users (not Beam committers/contributors). You
should ensure that Release Notes are informative and useful.</p>
