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 8631971 Publishing website 2021/03/15 18:07:53 at commit 5a9bb83
8631971 is described below
commit 8631971c93c4b29b4ec741aba9f8aab2fe62b7bb
Author: jenkins <[email protected]>
AuthorDate: Mon Mar 15 18:07:53 2021 +0000
Publishing website 2021/03/15 18:07:53 at commit 5a9bb83
---
website/generated-content/contribute/index.html | 11 +++--
website/generated-content/contribute/index.xml | 45 ++++++++++++---------
.../contribute/release-guide/index.html | 47 +++++++++++-----------
website/generated-content/sitemap.xml | 2 +-
4 files changed, 57 insertions(+), 48 deletions(-)
diff --git a/website/generated-content/contribute/index.html
b/website/generated-content/contribute/index.html
index 619953a..a736f2a 100644
--- a/website/generated-content/contribute/index.html
+++ b/website/generated-content/contribute/index.html
@@ -51,12 +51,15 @@ ASF Jira Username. For example <a
href=https://lists.apache.org/thread.html/e601
<a href=/community/contact-us/>discuss it on the dev@ mailing
list</a>.</li><li>For large changes create a design doc
(<a href=https://s.apache.org/beam-design-doc-template>template</a>,
<a href=https://s.apache.org/beam-design-docs>examples</a>) and email it to
the <a href=/community/contact-us>dev@ mailing list</a>.</li></ol><h3
id=development-setup>Development Setup</h3><ol><li><p>If you need help with git
forking, cloning, branching, committing, pull requests, and squashing commits,
see
-<a href=https://cwiki.apache.org/confluence/display/BEAM/Git+Tips>Git workflow
tips</a></p></li><li><p>Familiarize yourself with gradle and the project
structure. At the root of the git repository, run:</p><pre><code>$ ./gradlew
projects
+<a href=https://cwiki.apache.org/confluence/display/BEAM/Git+Tips>Git workflow
tips</a></p></li><li><p>Clone the git repository. You can download it anywhere
you like, however for Go development we recommend putting it in your <a
href=https://golang.org/doc/gopath_code#GOPATH><code>$GOPATH</code></a>
(<code>$HOME/go</code> by default on Unix systems).</p><pre><code>$ mkdir -p
~/go/src/github.com/apache
+$ cd ~/go/src/github.com/apache
+$ git clone https://github.com/apache/beam
+$ cd beam
+</code></pre></li><li><p>Familiarize yourself with gradle and the project
structure. At the root of the git repository, run:</p><pre><code>$ ./gradlew
projects
</code></pre><p>Examine the available tasks in a project. For the default set
of tasks, use:</p><pre><code>$ ./gradlew tasks
</code></pre><p>For a given module, use:</p><pre><code>$ ./gradlew -p
sdks/java/io/cassandra tasks
</code></pre><p>For an exhaustive list of tasks, use:</p><pre><code>$
./gradlew tasks --all
-</code></pre></li><li><p>Make sure you can build and run tests</p><p>Run the
entire set of tests with:</p><pre><code>$ ./gradlew check
-</code></pre><p>You can limit testing to a particular module. Gradle will
build just the necessary things to run those tests. For
example:</p><pre><code>$ ./gradlew -p sdks/go check
+</code></pre></li><li><p>Make sure you can build and run tests</p><p>Since
Beam is a large project, usually, you will want to limit testing to the
particular module you are working on. Gradle will build just the necessary
things to run those tests. For example:</p><pre><code>$ ./gradlew -p sdks/go
check
$ ./gradlew -p sdks/java/io/cassandra check
$ ./gradlew -p runners/flink check
</code></pre></li><li><p>Now you may want to set up your preferred IDE and
other aspects of your development
@@ -99,7 +102,7 @@ Anyone has read access. If you wish to contribute changes,
please create an acco
<a href=/contribute/ptransform-style-guide>PTransform Style
Guide</a>.</p><p>If you are contributing a Runner to Beam, refer to the
<a href=/contribute/runner-guide/>Runner authoring guide</a></p><p>Review <a
href=https://s.apache.org/beam-design-docs>design documents</a>.</p><p>A great
way to contribute is to join an existing effort. For the most
intensive efforts, check out the <a href=/roadmap/>roadmap</a>.</p><p>You can
also find a more exhaustive list on the <a
href=https://cwiki.apache.org/confluence/display/BEAM/Apache+Beam>Beam
developers’ wiki</a></p><h2 id=troubleshooting>Troubleshooting</h2><p>If
you run into any issues, check out the <a
href=https://cwiki.apache.org/confluence/display/BEAM/Contributor+FAQ>contribution
FAQ</a> or ask on the <a href=/community/contact-us/>dev@ mailing list</a> or
<a href=/community [...]
-<a href=/community/contact-us>reach out to the Beam community</a>.</p><div
class=feedback><p class=update>Last updated on 2021/02/05</p><h3>Have you found
everything you were looking for?</h3><p class=description>Was it all useful and
clear? Is there anything that you would like to change? Let us know!</p><button
class=load-button><a href="mailto:[email protected]?subject=Beam Website
Feedback">SEND FEEDBACK</a></button></div></div></div><footer class=footer><div
class=footer__containe [...]
+<a href=/community/contact-us>reach out to the Beam community</a>.</p><div
class=feedback><p class=update>Last updated on 2021/03/12</p><h3>Have you found
everything you were looking for?</h3><p class=description>Was it all useful and
clear? Is there anything that you would like to change? Let us know!</p><button
class=load-button><a href="mailto:[email protected]?subject=Beam Website
Feedback">SEND FEEDBACK</a></button></div></div></div><footer class=footer><div
class=footer__containe [...]
<a href=http://www.apache.org>The Apache Software Foundation</a>
| <a href=/privacy_policy>Privacy Policy</a>
| <a href=/feed.xml>RSS Feed</a><br><br>Apache Beam, Apache, Beam, the Beam
logo, and the Apache feather logo are either registered trademarks or
trademarks of The Apache Software Foundation. All other products or name brands
are trademarks of their respective holders, including The Apache Software
Foundation.</div></div></div></div></footer></body></html>
\ No newline at end of file
diff --git a/website/generated-content/contribute/index.xml
b/website/generated-content/contribute/index.xml
index 762515e..7e3b3e6 100644
--- a/website/generated-content/contribute/index.xml
+++ b/website/generated-content/contribute/index.xml
@@ -363,6 +363,7 @@ limitations under the License.
</ul>
</li>
<li><a href="#fix-any-issues">Fix any issues</a></li>
+<li><a href="#finalize-the-vote">Finalize the vote</a></li>
<li><a href="#checklist-to-proceed-to-the-next-step-2">Checklist to
proceed to the next step</a></li>
</ul>
</li>
@@ -1099,7 +1100,7 @@ ${CONTRIBUTORS}
<p>You can (optionally) also do additional verification by:</p>
<ol>
<li>Check that Python zip file contains the <code>README.md</code>,
<code>NOTICE</code>, and <code>LICENSE</code> files.</li>
-<li>Check hashes (e.g. <code>md5sum -c *.md5</code> and
<code>sha1sum -c *.sha1</code>)</li>
+<li>Check hashes (e.g. <code>md5sum -c *.md5</code> and
<code>sha1sum -c *.sha1</code>. Note that signature/checksum files of
Java artifacts may not contain filenames. Hence you might need to compare
checksums/signatures manually or modify the files by appending the
filenames.)</li>
<li>Check signatures (e.g. <code>gpg --verify
apache-beam-1.2.3-python.zip.asc apache-beam-1.2.3-python.zip</code>)</li>
<li><code>grep</code> for legal headers in each file.</li>
<li>Run all jenkins suites and include links to passing tests in the voting
email.</li>
@@ -1151,21 +1152,6 @@ There’s no need to wait 72 hours.
Proceed to the <code>Fix Issues</code> step below and address the
problem.
However, some issues don’t require cancellation.
For example, if an issue is found in the website pull request, just correct it
on the spot and the vote can continue as-is.</p>
-<p>If there are no issues, reply on the vote thread to close the voting.
-Then, tally the votes in a separate email thread.
-Here’s an email template; please adjust as you see fit.</p>
-<pre><code>From: Release Manager
-To: [email protected]
-Subject: [RESULT] [VOTE] Release 1.2.3, release candidate #3
-I'm happy to announce that we have unanimously approved this release.
-There are XXX approving votes, XXX of which are binding:
-* approver 1
-* approver 2
-* approver 3
-* approver 4
-There are no disapproving votes.
-Thanks everyone!
-</code></pre>
<h3 id="run-validation-tests">Run validation tests</h3>
<p>All tests listed in this <a
href="https://s.apache.org/beam-release-validation";>spreadsheet</a></p>
<p>Since there are a bunch of tests, we recommend you running validations
using automation script.
@@ -1423,11 +1409,32 @@ Additionally, any JIRA issues created from the initial
branch verification shoul
<p>Code changes should be proposed as standard pull requests to the
<code>master</code> branch and reviewed using the normal contributing
process.
Then, relevant changes should be cherry-picked into the release branch
proposed as pull requests against the release branch, again reviewed and merged
using the normal contributing process.</p>
<p>Once all issues have been resolved, you should go back and build a new
release candidate with these changes.</p>
+<h3 id="finalize-the-vote">Finalize the vote</h3>
+<p>Reply on the vote thread to close the voting once following conditions
are met for the current release candidate.</p>
+<ul>
+<li>At least 72 hours has passed since the voting email.</li>
+<li>No release blocking issues have been identified.</li>
+<li>Voting thread has at least three approving PMC votes.</li>
+</ul>
+<p>Then, tally the votes in a separate email thread.
+Here’s an email template; please adjust as you see fit.</p>
+<pre><code>From: Release Manager
+To: [email protected]
+Subject: [RESULT] [VOTE] Release 1.2.3, release candidate #3
+I'm happy to announce that we have unanimously approved this release.
+There are XXX approving votes, XXX of which are binding:
+* approver 1
+* approver 2
+* approver 3
+* approver 4
+There are no disapproving votes.
+Thanks everyone!
+</code></pre>
<h3 id="checklist-to-proceed-to-the-next-step-2">Checklist to proceed to
the next step</h3>
<ol>
<li>Issues identified during vote have been resolved, with fixes committed
to the release branch.</li>
<li>All issues tagged with <code>Fix-Version</code> for the current
release should be closed.</li>
-<li>Community votes to release the proposed candidate, with at least three
approving PMC votes</li>
+<li>Community votes to release the proposed candidate, with at least three
approving PMC votes.</li>
</ol>
<hr>
<h2 id="10-finalize-the-release">10. Finalize the release</h2>
@@ -1495,7 +1502,7 @@ The release manager should also make sure to update these
links on the website (
<p>In JIRA, inside <a
href="https://issues.apache.org/jira/plugins/servlet/project-config/BEAM/versions";>version
management</a>, hover over the current release and a settings menu will
appear.
Click <code>Release</code>, and select today’s date.</p>
<h4 id="recordkeeping-with-asf">Recordkeeping with ASF</h4>
-<p>Use reporter.apache.org to seed the information about the release into
future project reports.</p>
+<p>Use <a
href="https://reporter.apache.org/addrelease.html?beam";>reporter.apache.org</a>
to seed the information about the release into future project reports.</p>
<h3 id="checklist-to-proceed-to-the-next-step-3">Checklist to proceed to
the next step</h3>
<ul>
<li>Maven artifacts released and indexed in the <a
href="https://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.apache.beam%22";>Maven
Central Repository</a></li>
@@ -1516,7 +1523,7 @@ If you end up getting permissions errors ask on the
mailing list for assistance.
<p>Announce on the dev@ mailing list that the release has been
finished.</p>
<p>Announce on the release on the user@ mailing list, listing major
improvements and contributions.</p>
<p>Announce the release on the <a
href="mailto:[email protected]";>[email protected]</a> mailing list.
-<strong>NOTE</strong>: This can only be done from
<code>@apache.org</code> email address.</p>
+<strong>NOTE</strong>: This can only be done from
<code>@apache.org</code> email address. This email has to be in plain
text (no HTML tags).</p>
<h3 id="social-media">Social media</h3>
<p>Tweet, post on Facebook, LinkedIn, and other platforms.
Ask other contributors to do the same.</p>
diff --git a/website/generated-content/contribute/release-guide/index.html
b/website/generated-content/contribute/release-guide/index.html
index c80ee86..63dad25 100644
--- a/website/generated-content/contribute/release-guide/index.html
+++ b/website/generated-content/contribute/release-guide/index.html
@@ -18,7 +18,7 @@
function addPlaceholder(){$('input:text').attr('placeholder',"What are you
looking for?");}
function endSearch(){var
search=document.querySelector(".searchBar");search.classList.add("disappear");var
icons=document.querySelector("#iconsBar");icons.classList.remove("disappear");}
function blockScroll(){$("body").toggleClass("fixedPosition");}
-function openMenu(){addPlaceholder();blockScroll();}</script><div
class="clearfix container-main-content"><div class="section-nav closed"
data-offset-top=90 data-offset-bottom=500><span class="section-nav-back
glyphicon glyphicon-menu-left"></span><nav><ul class=section-nav-list
data-section-nav><li><span
class=section-nav-list-main-title>Contribute</span></li><li><a
href=/contribute/>Get started contributing</a></li><li><a
href=/contribute/get-help/>Get Help</a></li><li><a href=/contrib [...]
+function openMenu(){addPlaceholder();blockScroll();}</script><div
class="clearfix container-main-content"><div class="section-nav closed"
data-offset-top=90 data-offset-bottom=500><span class="section-nav-back
glyphicon glyphicon-menu-left"></span><nav><ul class=section-nav-list
data-section-nav><li><span
class=section-nav-list-main-title>Contribute</span></li><li><a
href=/contribute/>Get started contributing</a></li><li><a
href=/contribute/get-help/>Get Help</a></li><li><a href=/contrib [...]
A release is one or more packages of the project artifact(s) that are approved
for general public distribution and use.
They may come with various degrees of caveat regarding their perceived quality
and potential for change, such as “alpha”, “beta”, “incubating”, “stable”,
etc.</p><p>The Beam community treats releases with great importance.
They are a public face of the project and most users interact with the project
only through the releases. Releases are signed off by the entire Beam community
in a public vote.</p><p>Each release is executed by a <em>Release Manager</em>,
who is selected among the Beam committers.
@@ -236,7 +236,7 @@ For more information on changes in {$RELEASE_VERSION},
check out the [detailed r
According to git shortlog, the following people contributed to the
{$RELEASE_VERSION} release. Thank you to all contributors!
${CONTRIBUTORS}
-</code></pre><h4 id=checklist-to-proceed-to-the-next-step-1>Checklist to
proceed to the next step</h4><ol><li>Maven artifacts deployed to the staging
repository of <a
href=https://repository.apache.org/content/repositories/>repository.apache.org</a></li><li>Source
distribution deployed to the dev repository of <a
href=https://dist.apache.org/repos/dist/dev/beam/>dist.apache.org</a></li><li>Website
pull request proposed to list the <a href=/get-started/downloads/>release</a>,
publish the [...]
+</code></pre><h4 id=checklist-to-proceed-to-the-next-step-1>Checklist to
proceed to the next step</h4><ol><li>Maven artifacts deployed to the staging
repository of <a
href=https://repository.apache.org/content/repositories/>repository.apache.org</a></li><li>Source
distribution deployed to the dev repository of <a
href=https://dist.apache.org/repos/dist/dev/beam/>dist.apache.org</a></li><li>Website
pull request proposed to list the <a href=/get-started/downloads/>release</a>,
publish the [...]
docker pull apache/beam_python3.5_sdk:2.16.0_rc1
</code></pre><hr><h2 id=9-vote-and-validate-release-candidate>9. Vote and
validate release candidate</h2><p>Once you have built and individually reviewed
the release candidate, please share it for the community-wide review.
Please review foundation-wide <a
href=http://www.apache.org/foundation/voting.html>voting guidelines</a> for
more information.</p><p>Start the review-and-vote thread on the dev@ mailing
list.
@@ -283,24 +283,7 @@ Release Manager
There’s no need to wait 72 hours.
Proceed to the <code>Fix Issues</code> step below and address the problem.
However, some issues don’t require cancellation.
-For example, if an issue is found in the website pull request, just correct it
on the spot and the vote can continue as-is.</p><p>If there are no issues,
reply on the vote thread to close the voting.
-Then, tally the votes in a separate email thread.
-Here’s an email template; please adjust as you see fit.</p><pre><code>From:
Release Manager
-To: [email protected]
-Subject: [RESULT] [VOTE] Release 1.2.3, release candidate #3
-
-I'm happy to announce that we have unanimously approved this release.
-
-There are XXX approving votes, XXX of which are binding:
-* approver 1
-* approver 2
-* approver 3
-* approver 4
-
-There are no disapproving votes.
-
-Thanks everyone!
-</code></pre><h3 id=run-validation-tests>Run validation tests</h3><p>All tests
listed in this <a
href=https://s.apache.org/beam-release-validation>spreadsheet</a></p><p>Since
there are a bunch of tests, we recommend you running validations using
automation script.
+For example, if an issue is found in the website pull request, just correct it
on the spot and the vote can continue as-is.</p><h3 id=run-validation-tests>Run
validation tests</h3><p>All tests listed in this <a
href=https://s.apache.org/beam-release-validation>spreadsheet</a></p><p>Since
there are a bunch of tests, we recommend you running validations using
automation script.
In case of script failure, you can still run all of them manually.</p><h4
id=run-validations-using-run_rc_validationsh>Run validations using
run_rc_validation.sh</h4><ul><li><p><strong>Script:</strong> <a
href=https://github.com/apache/beam/blob/master/release/src/main/scripts/run_rc_validation.sh>run_rc_validation.sh</a></p></li><li><p><strong>Usage</strong></p><ol><li>First
update required configurations listed in <code>RC_VALIDATE_CONFIGS</code> in
<a
href=https://github.com/apache/beam/blob/master/release/src/main/scripts/script.config>script.config</a></li><li>Then
run<pre><code>./beam/release/src/main/scripts/run_rc_validation.sh
</code></pre></li></ol></li><li><p><strong>Tasks
included</strong></p><ol><li>Run Java quickstart with Direct Runner, Flink
local runner, Spark local runner and Dataflow runner.</li><li>Run Java Mobile
Games(UserScore, HourlyTeamScore, Leaderboard) with Dataflow
runner.</li><li>Create a PR to trigger python validation job,
including<ul><li>Python quickstart in batch and streaming mode with direct
runner and Dataflow runner.</li><li>Python Mobile Games(UserScore,
HourlyTeamScore) with dir [...]
@@ -402,7 +385,23 @@ mvn compile exec:java
-Dexec.mainClass=org.apache.beam.examples.complete.game.in
--fixed_window_duration ${SOME_SMALL_DURATION}
</code></pre><p>Inspect results:</p><ul><li>Goto your Dataflow job console and
check whether there is any error.</li><li>Goto your BigQuery console and check
whether your ${USER}_test has game_stats_teams and game_stats_sessions
table.</li><li>bq head -n 10 ${USER}_test.game_stats_teams</li><li>bq head -n
10 ${USER}_test.game_stats_sessions</li></ul></li></ul></li></ul><h3
id=fix-any-issues>Fix any issues</h3><p>Any issues identified during the
community review and vote should be fixed i [...]
Additionally, any JIRA issues created from the initial branch verification
should be fixed.</p><p>Code changes should be proposed as standard pull
requests to the <code>master</code> branch and reviewed using the normal
contributing process.
-Then, relevant changes should be cherry-picked into the release branch
proposed as pull requests against the release branch, again reviewed and merged
using the normal contributing process.</p><p>Once all issues have been
resolved, you should go back and build a new release candidate with these
changes.</p><h3 id=checklist-to-proceed-to-the-next-step-2>Checklist to proceed
to the next step</h3><ol><li>Issues identified during vote have been resolved,
with fixes committed to the release b [...]
+Then, relevant changes should be cherry-picked into the release branch
proposed as pull requests against the release branch, again reviewed and merged
using the normal contributing process.</p><p>Once all issues have been
resolved, you should go back and build a new release candidate with these
changes.</p><h3 id=finalize-the-vote>Finalize the vote</h3><p>Reply on the vote
thread to close the voting once following conditions are met for the current
release candidate.</p><ul><li>At least [...]
+Here’s an email template; please adjust as you see fit.</p><pre><code>From:
Release Manager
+To: [email protected]
+Subject: [RESULT] [VOTE] Release 1.2.3, release candidate #3
+
+I'm happy to announce that we have unanimously approved this release.
+
+There are XXX approving votes, XXX of which are binding:
+* approver 1
+* approver 2
+* approver 3
+* approver 4
+
+There are no disapproving votes.
+
+Thanks everyone!
+</code></pre><h3 id=checklist-to-proceed-to-the-next-step-2>Checklist to
proceed to the next step</h3><ol><li>Issues identified during vote have been
resolved, with fixes committed to the release branch.</li><li>All issues tagged
with <code>Fix-Version</code> for the current release should be
closed.</li><li>Community votes to release the proposed candidate, with at
least three approving PMC votes.</li></ol><hr><h2
id=10-finalize-the-release>10. Finalize the release</h2><p>Once the relea [...]
This involves the final deployment of the release candidate to the release
repositories, merging of the website changes, etc.</p><h3
id=deploy-artifacts-to-maven-central-repository>Deploy artifacts to Maven
Central Repository</h3><p>Use the <a
href=https://repository.apache.org/#stagingRepositories>Apache Nexus repository
manager</a> to release the staged binary artifacts to the Maven Central
repository.
In the <code>Staging Repositories</code> section, find the relevant release
candidate <code>orgapachebeam-XXX</code> entry and click <code>Release</code>.
Drop all other release candidates that are not being
released.</p><p><strong>NOTE</strong>: If you are using <a
href=https://help.github.com/articles/securing-your-account-with-two-factor-authentication-2fa/>GitHub
two-factor authentication</a> and haven’t configure HTTPS access,
@@ -418,14 +417,14 @@ git push https://github.com/apache/beam
"$VERSION_TAG"
Ping <a href=mailto:[email protected]>dev@</a> for assistance if you need
it.</p><h4 id=deploy-source-release-to-distapacheorg>Deploy source release to
dist.apache.org</h4><p>Copy the source release from the <code>dev</code>
repository to the <code>release</code> repository at
<code>dist.apache.org</code> using Subversion.</p><p>Make sure the last
release’s artifacts have been copied from <code>dist.apache.org</code> to
<code>archive.apache.org</code>.
This should happen automatically: <a
href=https://lists.apache.org/thread.html/39c26c57c5125a7ca06c3c9315b4917b86cd0e4567b7174f4bc4d63b%40%3Cdev.beam.apache.org%3E>dev@
thread</a> with context.
The release manager should also make sure to update these links on the website
(<a href=https://github.com/apache/beam/pull/11727>example</a>).</p><h4
id=mark-the-version-as-released-in-jira>Mark the version as released in
JIRA</h4><p>In JIRA, inside <a
href=https://issues.apache.org/jira/plugins/servlet/project-config/BEAM/versions>version
management</a>, hover over the current release and a settings menu will appear.
-Click <code>Release</code>, and select today’s date.</p><h4
id=recordkeeping-with-asf>Recordkeeping with ASF</h4><p>Use reporter.apache.org
to seed the information about the release into future project reports.</p><h3
id=checklist-to-proceed-to-the-next-step-3>Checklist to proceed to the next
step</h3><ul><li>Maven artifacts released and indexed in the <a
href=https://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.apache.beam%22>Maven
Central Repository</a></li><li>Source distribution av [...]
+Click <code>Release</code>, and select today’s date.</p><h4
id=recordkeeping-with-asf>Recordkeeping with ASF</h4><p>Use <a
href=https://reporter.apache.org/addrelease.html?beam>reporter.apache.org</a>
to seed the information about the release into future project reports.</p><h3
id=checklist-to-proceed-to-the-next-step-3>Checklist to proceed to the next
step</h3><ul><li>Maven artifacts released and indexed in the <a
href=https://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.apache.beam%2 [...]
(Note: Not all committers have administrator access to JIRA.
If you end up getting permissions errors ask on the mailing list for
assistance.)</li><li>Release version is listed at
reporter.apache.org</li></ul><hr><h2 id=11-promote-the-release>11. Promote the
release</h2><p>Once the release has been finalized, the last step of the
process is to promote the release within the project and beyond.</p><h3
id=apache-mailing-lists>Apache mailing lists</h3><p>Announce on the dev@
mailing list that the release has been finished.</p><p>Announce on the relea
[...]
-<strong>NOTE</strong>: This can only be done from <code>@apache.org</code>
email address.</p><h3 id=social-media>Social media</h3><p>Tweet, post on
Facebook, LinkedIn, and other platforms.
+<strong>NOTE</strong>: This can only be done from <code>@apache.org</code>
email address. This email has to be in plain text (no HTML tags).</p><h3
id=social-media>Social media</h3><p>Tweet, post on Facebook, LinkedIn, and
other platforms.
Ask other contributors to do the same.</p><p>Also, update <a
href=https://en.wikipedia.org/wiki/Apache_Beam>the Wikipedia article on Apache
Beam</a>.</p><h3 id=checklist-to-declare-the-process-completed>Checklist to
declare the process completed</h3><ol><li>Release announced on the user@
mailing list.</li><li>Blog post published, if applicable.</li><li>Release
recorded in reporter.apache.org.</li><li>Release announced on social
media.</li><li>Completion declared on the dev@ mailing list. [...]
Once you’ve finished the release, please take a step back and look what areas
of this process and be improved. Perhaps some part of the process can be
simplified.
Perhaps parts of this guide can be clarified.</p><p>If we have specific ideas,
please start a discussion on the dev@ mailing list and/or propose a pull
request to update this guide.
-Thanks!</p><div class=feedback><p class=update>Last updated on
2021/01/22</p><h3>Have you found everything you were looking for?</h3><p
class=description>Was it all useful and clear? Is there anything that you would
like to change? Let us know!</p><button class=load-button><a
href="mailto:[email protected]?subject=Beam Website Feedback">SEND
FEEDBACK</a></button></div></div></div><footer class=footer><div
class=footer__contained><div class=footer__cols><div class="footer__cols__col
foo [...]
+Thanks!</p><div class=feedback><p class=update>Last updated on
2021/03/15</p><h3>Have you found everything you were looking for?</h3><p
class=description>Was it all useful and clear? Is there anything that you would
like to change? Let us know!</p><button class=load-button><a
href="mailto:[email protected]?subject=Beam Website Feedback">SEND
FEEDBACK</a></button></div></div></div><footer class=footer><div
class=footer__contained><div class=footer__cols><div class="footer__cols__col
foo [...]
<a href=http://www.apache.org>The Apache Software Foundation</a>
| <a href=/privacy_policy>Privacy Policy</a>
| <a href=/feed.xml>RSS Feed</a><br><br>Apache Beam, Apache, Beam, the Beam
logo, and the Apache feather logo are either registered trademarks or
trademarks of The Apache Software Foundation. All other products or name brands
are trademarks of their respective holders, including The Apache Software
Foundation.</div></div></div></div></footer></body></html>
\ No newline at end of file
diff --git a/website/generated-content/sitemap.xml
b/website/generated-content/sitemap.xml
index 2bc720f..7d589ae 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>/blog/beam-2.28.0/</loc><lastmod>2021-02-22T11:40:20-08:00</lastmod></url><url><loc>/categories/blog/</loc><lastmod>2021-02-22T11:40:20-08:00</lastmod></url><url><loc>/blog/</loc><lastmod>2021-02-22T11:40:20-08:00</lastmod></url><url><loc>/categories/</loc><lastmod>2021-02-23T13:40:55+01:00</lastmod></url><url><loc>/blog/k
[...]
\ 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>/blog/beam-2.28.0/</loc><lastmod>2021-02-22T11:40:20-08:00</lastmod></url><url><loc>/categories/blog/</loc><lastmod>2021-02-22T11:40:20-08:00</lastmod></url><url><loc>/blog/</loc><lastmod>2021-02-22T11:40:20-08:00</lastmod></url><url><loc>/categories/</loc><lastmod>2021-02-23T13:40:55+01:00</lastmod></url><url><loc>/blog/k
[...]
\ No newline at end of file
