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 f2472e9 Publishing website 2019/12/19 00:50:42 at commit 166ed81
f2472e9 is described below
commit f2472e9d4ea11205dc42f1dcf0b811dd17fa2a7b
Author: jenkins <[email protected]>
AuthorDate: Thu Dec 19 00:50:42 2019 +0000
Publishing website 2019/12/19 00:50:42 at commit 166ed81
---
.../generated-content/contribute/release-guide/index.html | 15 +++++++++++++++
1 file changed, 15 insertions(+)
diff --git a/website/generated-content/contribute/release-guide/index.html
b/website/generated-content/contribute/release-guide/index.html
index 7306ac4..67652dc 100644
--- a/website/generated-content/contribute/release-guide/index.html
+++ b/website/generated-content/contribute/release-guide/index.html
@@ -1024,6 +1024,20 @@ to find environment issues this way without having to
wait until the full build
<p>Check if there are outstanding cherry-picks into the release branch, <a
href="https://github.com/apache/beam/pulls?utf8=%E2%9C%93&q=is%3Apr+base%3Arelease-2.14.0";>e.g.
for <code class="highlighter-rouge">2.14.0</code></a>.
Make sure they have blocker JIRAs attached and are OK to get into the release
by checking with community if needed.</p>
+<p>As the Release Manager you are empowered to accept or reject cherry-picks
to the release branch. You are encouraged to ask the following questions to be
answered on each cherry-pick PR and you can choose to reject cherry-pick
requests if these questions are not satisfactorily answered:</p>
+
+<ul>
+ <li>Is this a regression from a previous release? (If no, fix could go to a
newer version.)</li>
+ <li>Is this a new feature or related to a new feature? (If yes, fix could go
to a new version.)</li>
+ <li>Would this impact production workloads for users? (E.g. if this is a
direct runner only fix it may not need to be a cherry pick.)</li>
+ <li>What percentage of users would be impacted by this issue if it is not
fixed? (E.g. If this is predicted to be a small number it may not need to be a
cherry pick.)</li>
+ <li>Would it be possible for the impacted users to skip this version? (If
users could skip this version, fix could go to a newer version.)</li>
+</ul>
+
+<p>It is important to accept major/blocking fixes to isolated issues to make a
higher quality release. However, beyond that each cherry pick will increase the
time required for the release and add more last minute code to the release
branch. Neither late releases nor not fully tested code will provide positive
user value.</p>
+
+<p><em>Tip</em>: Another tool in your toolbox is the known issues section of
the release blog. Consider adding known issues there for minor issues instead
of accepting cherry picks to the release branch.</p>
+
<hr />
<h2 id="5-build-a-release-candidate">5. Build a release candidate</h2>
@@ -1398,6 +1412,7 @@ all major features and bug fixes, and all known
issues.</p>
* {$KNOWN_ISSUE_1}
* {$KNOWN_ISSUE_2}
+ * See a full list of open [issues that
affects](https://issues.apache.org/jira/browse/BEAM-8989?jql=project = BEAM AND
affectedVersion = 2.16.0 ORDER BY priority DESC, updated DESC) this version.
## List of Contributors
