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 3bd4dca Publishing website 2020/06/03 00:07:27 at commit 071b0fa
3bd4dca is described below
commit 3bd4dca87575802e814f323a02cf1132c5a5245b
Author: jenkins <[email protected]>
AuthorDate: Wed Jun 3 00:07:27 2020 +0000
Publishing website 2020/06/03 00:07:27 at commit 071b0fa
---
website/generated-content/blog/beam-2.21.0/index.html | 2 +-
website/generated-content/blog/index.xml | 2 +-
website/generated-content/categories/blog/index.xml | 2 +-
website/generated-content/contribute/index.xml | 13 -------------
.../generated-content/contribute/release-guide/index.html | 6 +++---
website/generated-content/feed.xml | 2 +-
website/generated-content/sitemap.xml | 2 +-
7 files changed, 8 insertions(+), 21 deletions(-)
diff --git a/website/generated-content/blog/beam-2.21.0/index.html
b/website/generated-content/blog/beam-2.21.0/index.html
index 0ec2a76..3da1bd1 100644
--- a/website/generated-content/blog/beam-2.21.0/index.html
+++ b/website/generated-content/blog/beam-2.21.0/index.html
@@ -3,7 +3,7 @@
<span class=icon-bar></span><span class=icon-bar></span><span
class=icon-bar></span></button>
<a href=/ class=navbar-brand><img alt=Brand style=height:25px
src=/images/beam_logo_navbar.png></a></div><div class="navbar-mask
closed"></div><div id=navbar class="navbar-container closed"><ul class="nav
navbar-nav"><li><a href=/get-started/beam-overview/>Get Started</a></li><li><a
href=/documentation/>Documentation</a></li><li><a
href=/documentation/sdks/java/>Languages</a></li><li><a
href=/documentation/runners/capability-matrix/>RUNNERS</a></li><li><a
href=/roadmap/>Roadmap</a></li>< [...]
•</p></header><div class=post-content itemprop=articleBody><p>We are happy to
present the new 2.21.0 release of Beam. This release includes both improvements
and new functionality.
-See the <a href=/get-started/downloads/#xxxx-xxxx>download page</a> for this
release.
+See the <a href=/get-started/downloads/#2210-2020-05-27>download page</a> for
this release.
For more information on changes in 2.21.0, check out the
<a
href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527&version=12347143";>detailed
release notes</a>.</p><h2 id=ios>I/Os</h2><ul><li>Python: Deprecated module
<code>apache_beam.io.gcp.datastore.v1</code> has been removed
as the client it uses is out of date and does not support Python 3
diff --git a/website/generated-content/blog/index.xml
b/website/generated-content/blog/index.xml
index 3b864c1..938db8e 100644
--- a/website/generated-content/blog/index.xml
+++ b/website/generated-content/blog/index.xml
@@ -109,7 +109,7 @@ See the License for the specific language governing
permissions and
limitations under the License.
-->
<p>We are happy to present the new 2.21.0 release of Beam. This release
includes both improvements and new functionality.
-See the <a href="/get-started/downloads/#xxxx-xxxx">download page</a>
for this release.
+See the <a href="/get-started/downloads/#2210-2020-05-27">download
page</a> for this release.
For more information on changes in 2.21.0, check out the
<a
href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527&amp;version=12347143";>detailed
release notes</a>.</p>
<h2 id="ios">I/Os</h2>
diff --git a/website/generated-content/categories/blog/index.xml
b/website/generated-content/categories/blog/index.xml
index d7e480b..a406291 100644
--- a/website/generated-content/categories/blog/index.xml
+++ b/website/generated-content/categories/blog/index.xml
@@ -109,7 +109,7 @@ See the License for the specific language governing
permissions and
limitations under the License.
-->
<p>We are happy to present the new 2.21.0 release of Beam. This release
includes both improvements and new functionality.
-See the <a href="/get-started/downloads/#xxxx-xxxx">download page</a>
for this release.
+See the <a href="/get-started/downloads/#2210-2020-05-27">download
page</a> for this release.
For more information on changes in 2.21.0, check out the
<a
href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527&amp;version=12347143";>detailed
release notes</a>.</p>
<h2 id="ios">I/Os</h2>
diff --git a/website/generated-content/contribute/index.xml
b/website/generated-content/contribute/index.xml
index 15cf853..3be532d 100644
--- a/website/generated-content/contribute/index.xml
+++ b/website/generated-content/contribute/index.xml
@@ -266,7 +266,6 @@ limitations under the License.
</li>
<li><a href="#4-triage-release-blocking-issues-in-jira">4. Triage
release-blocking issues in JIRA</a>
<ul>
-<li><a href="#review-release-notes-in-jira">Review Release Notes in
JIRA</a></li>
<li><a href="#review-cherry-picks">Review cherry-picks</a></li>
</ul>
</li>
@@ -803,17 +802,6 @@ to find environment issues this way without having to wait
until the full build
<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>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>
-<p>Open the release notes from the <a
href="https://issues.apache.org/jira/browse/BEAM/?selectedTab=com.atlassian.jira.jira-projects-plugin:versions-panel";>version
status page</a> by choosing the release underway and clicking Release
Notes.</p>
-<p>You should verify that the issues listed automatically by JIRA are
appropriate to appear in the Release Notes. Specifically, issues should:</p>
-<ul>
-<li>Be appropriately classified as <code>Bug</code>, <code>New
Feature</code>, <code>Improvement</code>, etc.</li>
-<li>Represent noteworthy user-facing changes, such as new functionality,
backward-incompatible API changes, or performance improvements.</li>
-<li>Have occurred since the previous release; an issue that was introduced
and fixed between releases should not appear in the Release Notes.</li>
-<li>Have an issue title that makes sense when read on its own.</li>
-</ul>
-<p>Adjust any of the above properties to the improve clarity and
presentation of the Release Notes.</p>
<h3 id="review-cherry-picks">Review cherry-picks</h3>
<p>Check if there are outstanding cherry-picks into the release branch,
<a
href="https://github.com/apache/beam/pulls?utf8=%E2%9C%93&amp;q=is%3Apr+base%3Arelease-2.14.0";>e.g.
for <code>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>
@@ -838,7 +826,6 @@ Make sure they have blocker JIRAs attached and are OK to
get into the release by
<li>JIRA release item for the subsequent release has been created;</li>
<li>All test failures from branch verification have associated JIRA
issues;</li>
<li>There are no release blocking JIRA issues;</li>
-<li>Release Notes in JIRA have been audited and adjusted;</li>
<li>Combined javadoc has the appropriate contents;</li>
<li>Release branch has been created;</li>
<li>There are no open pull requests to release branch;</li>
diff --git a/website/generated-content/contribute/release-guide/index.html
b/website/generated-content/contribute/release-guide/index.html
index a10c45b..ccec0eb 100644
--- a/website/generated-content/contribute/release-guide/index.html
+++ b/website/generated-content/contribute/release-guide/index.html
@@ -1,7 +1,7 @@
<!doctype html><html lang=en class=no-js><head><meta charset=utf-8><meta
http-equiv=x-ua-compatible content="IE=edge"><meta name=viewport
content="width=device-width,initial-scale=1"><title>Beam Release
Guide</title><meta name=description content="Apache Beam is an open source,
unified model and set of language-specific SDKs for defining and executing data
processing workflows, and also data ingestion and integration flows, supporting
Enterprise Integration Patterns (EIPs) and Domain Spe [...]
<span class=sr-only>Toggle navigation</span>
<span class=icon-bar></span><span class=icon-bar></span><span
class=icon-bar></span></button>
-<a href=/ class=navbar-brand><img alt=Brand style=height:25px
src=/images/beam_logo_navbar.png></a></div><div class="navbar-mask
closed"></div><div id=navbar class="navbar-container closed"><ul class="nav
navbar-nav"><li><a href=/get-started/beam-overview/>Get Started</a></li><li><a
href=/documentation/>Documentation</a></li><li><a
href=/documentation/sdks/java/>Languages</a></li><li><a
href=/documentation/runners/capability-matrix/>RUNNERS</a></li><li><a
href=/roadmap/>Roadmap</a></li>< [...]
+<a href=/ class=navbar-brand><img alt=Brand style=height:25px
src=/images/beam_logo_navbar.png></a></div><div class="navbar-mask
closed"></div><div id=navbar class="navbar-container closed"><ul class="nav
navbar-nav"><li><a href=/get-started/beam-overview/>Get Started</a></li><li><a
href=/documentation/>Documentation</a></li><li><a
href=/documentation/sdks/java/>Languages</a></li><li><a
href=/documentation/runners/capability-matrix/>RUNNERS</a></li><li><a
href=/roadmap/>Roadmap</a></li>< [...]
please follow <a
href=https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/>the
guide</a> to configure command line access.</p><h3
id=accounts>Accounts</h3><p>Please have these credentials ready at hand, you
will likely need to enter them multiple times:</p><ul><li>GPG pass phrase (see
the next section);</li><li>Apache ID and Password;</li><li>GitHub ID and
Password.</li><li>DockerHub ID and Password. (You should be a member of
maintainer team; email at [...]
or running all commands manually.</p><h5
id=use-preparation_before_releasesh-to-setup-gpg>Use
preparation_before_release.sh to setup GPG</h5><ul><li><p>Script: <a
href=https://github.com/apache/beam/blob/master/release/src/main/scripts/preparation_before_release.sh>preparation_before_release.sh</a></p></li><li><p>Usage</p><pre><code>./beam/release/src/main/scripts/preparation_before_release.sh
</code></pre></li><li><p>Tasks included</p><ol><li><p>Help you create a new
GPG key if you want.</p></li><li><p>Configure <code>git user.signingkey</code>
with chosen pubkey.</p></li><li><p>Add chosen pubkey into <a
href=https://dist.apache.org/repos/dist/dev/beam/KEYS>dev KEYS</a> and <a
href=https://dist.apache.org/repos/dist/release/beam/KEYS>release
KEYS</a></p><p><strong>NOTES</strong>: Only PMC can write into <a
href=https://dist.apache.org/repos/dist/release/beam/>release repo</a> [...]
@@ -123,8 +123,8 @@ sudo apt-get install python3.7-dev
</code></pre></li><li><p>Run build command</p><pre><code>./gradlew build
-PisRelease --no-parallel --scan --stacktrace --continue
</code></pre><p>To speed things up locally you might want to omit
<code>--no-parallel</code>. You can also omit <code>--continue</code>
if you want build fails after the first error instead of continuing, it may be
easier and faster
-to find environment issues this way without having to wait until the full
build completes.</p></li></ol></li></ul><h4
id=create-release-blocking-issues-in-jira>Create release-blocking issues in
JIRA</h4><p>The verify_release_build.sh script may include failing or flaky
tests. For each of the failing tests create a JIRA with the following
properties:</p><ul><li><p>Issue Type: Bug</p></li><li><p>Summary: Name of
failing gradle task and name of failing test (where applicable) in form of :My
[...]
-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 [...]
+to find environment issues this way without having to wait until the full
build completes.</p></li></ol></li></ul><h4
id=create-release-blocking-issues-in-jira>Create release-blocking issues in
JIRA</h4><p>The verify_release_build.sh script may include failing or flaky
tests. For each of the failing tests create a JIRA with the following
properties:</p><ul><li><p>Issue Type: Bug</p></li><li><p>Summary: Name of
failing gradle task and name of failing test (where applicable) in form of :My
[...]
+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 [...]
</code></pre></li><li><p>The script will:</p><ol><li>Run gradle release to
create rc tag and push source release into github repo.</li><li>Run gradle
publish to push java artifacts into Maven staging repo.</li><li>Stage source
release into dist.apache.org dev <a
href=https://dist.apache.org/repos/dist/dev/beam/>repo</a>.</li><li>Stage,sign
and hash python binaries into dist.apache.ord dev repo python dir</li><li>Stage
SDK docker images to <a href="https://hub.docker.com/search?q=apache%2 [...]
Please note that dependencies for the SDKs with different Python versions vary.
Need to verify all Python images by replacing <code>${ver}</code> with each
supported Python version <code>X.Y</code>.</li></ul><pre><code>docker run -it
--entrypoint=/bin/bash apache/beam_python${ver}_sdk:${RELEASE}_rc{RC_NUM}
diff --git a/website/generated-content/feed.xml
b/website/generated-content/feed.xml
index 7675bbc..8ed79f3 100644
--- a/website/generated-content/feed.xml
+++ b/website/generated-content/feed.xml
@@ -109,7 +109,7 @@ See the License for the specific language governing
permissions and
limitations under the License.
-->
<p>We are happy to present the new 2.21.0 release of Beam. This release
includes both improvements and new functionality.
-See the <a href="/get-started/downloads/#xxxx-xxxx">download page</a>
for this release.
+See the <a href="/get-started/downloads/#2210-2020-05-27">download
page</a> for this release.
For more information on changes in 2.21.0, check out the
<a
href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527&amp;version=12347143";>detailed
release notes</a>.</p>
<h2 id="ios">I/Os</h2>
diff --git a/website/generated-content/sitemap.xml
b/website/generated-content/sitemap.xml
index 312a332..21d9754 100644
--- a/website/generated-content/sitemap.xml
+++ b/website/generated-content/sitemap.xml
@@ -1 +1 @@
-<?xml version="1.0" encoding="utf-8" standalone="yes"?><urlset
xmlns="http://www.sitemaps.org/schemas/sitemap/0.9";
xmlns:xhtml="http://www.w3.org/1999/xhtml";><url><loc>/categories/blog/</loc><lastmod>2020-05-28T15:14:36-07:00</lastmod></url><url><loc>/blog/</loc><lastmod>2020-05-28T15:14:36-07:00</lastmod></url><url><loc>/categories/</loc><lastmod>2020-05-28T15:14:36-07:00</lastmod></url><url><loc>/categories/python/</loc><lastmod>2020-05-28T15:14:36-07:00</lastmod></url><url><loc>/blog/
[...]
\ No newline at end of file
+<?xml version="1.0" encoding="utf-8" standalone="yes"?><urlset
xmlns="http://www.sitemaps.org/schemas/sitemap/0.9";
xmlns:xhtml="http://www.w3.org/1999/xhtml";><url><loc>/categories/blog/</loc><lastmod>2020-06-01T15:15:07-04:00</lastmod></url><url><loc>/blog/</loc><lastmod>2020-06-01T15:15:07-04:00</lastmod></url><url><loc>/categories/</loc><lastmod>2020-06-01T15:15:07-04:00</lastmod></url><url><loc>/categories/python/</loc><lastmod>2020-05-28T15:14:36-07:00</lastmod></url><url><loc>/blog/
[...]
\ No newline at end of file
