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 78269ef  Publishing website 2022/02/12 06:06:32 at commit 7fa5387
78269ef is described below

commit 78269efed0f0bb7c8b5b7120b32b89ebb8e6fbc1
Author: jenkins <[email protected]>
AuthorDate: Sat Feb 12 06:06:32 2022 +0000

    Publishing website 2022/02/12 06:06:32 at commit 7fa5387
---
 website/generated-content/contribute/index.xml                | 2 +-
 website/generated-content/contribute/release-guide/index.html | 4 ++--
 website/generated-content/sitemap.xml                         | 2 +-
 3 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/website/generated-content/contribute/index.xml 
b/website/generated-content/contribute/index.xml
index 77a58f9..ed1d3d7 100644
--- a/website/generated-content/contribute/index.xml
+++ b/website/generated-content/contribute/index.xml
@@ -594,7 +594,7 @@ Measurements are available on &lt;a 
href="http://metrics.beam.apache.org";>metric
 &lt;p>All Runners which publish data should be checked for the following, in 
both &lt;em>batch&lt;/em> and &lt;em>streaming&lt;/em> mode:&lt;/p>
 &lt;ul>
 &lt;li>&lt;a 
href="http://metrics.beam.apache.org/d/MOi-kf3Zk/pardo-load-tests";>ParDo&lt;/a> 
and &lt;a 
href="http://metrics.beam.apache.org/d/UYZ-oJ3Zk/gbk-load-test";>GBK&lt;/a>: 
Runtime, latency, checkpoint duration&lt;/li>
-&lt;li>&lt;a 
href="http://metrics.beam.apache.org/d/ahuaA_zGz/nexmark";>Nexmark&lt;/a>: Query 
runtime for all queries&lt;/li>
+&lt;li>&lt;a 
href="http://metrics.beam.apache.org/d/ahudA_zGz/nexmark";>Nexmark&lt;/a>: Query 
runtime for all queries&lt;/li>
 &lt;li>&lt;a 
href="http://metrics.beam.apache.org/d/bnlHKP3Wz/java-io-it-tests-dataflow";>IO&lt;/a>:
 Runtime&lt;/li>
 &lt;/ul>
 &lt;p>If regressions are found, the release branch can still be created, but 
the regressions should be investigated and fixed as part of the release process.
diff --git a/website/generated-content/contribute/release-guide/index.html 
b/website/generated-content/contribute/release-guide/index.html
index a69b10d..6daf98e 100644
--- a/website/generated-content/contribute/release-guide/index.html
+++ b/website/generated-content/contribute/release-guide/index.html
@@ -77,7 +77,7 @@ With the release currently underway, new issues should be 
resolved against a sub
 Therefore, you should create a release item for this subsequent release, as 
follows:</p><p><strong>Attention</strong>: Only PMC has permission to perform 
this.
 If you are not a PMC, please ask for help in dev@ mailing list.</p><ol><li>In 
JIRA, navigate to <a 
href=https://issues.apache.org/jira/plugins/servlet/project-config/BEAM/versions><code>Beam
 > Administration > Versions</code></a>.</li><li>Add a new release. Choose the 
next minor version number after the version currently underway, select the 
release cut date (today’s date) as the <code>Start Date</code>, and choose 
<code>Add</code>.</li><li>At the end of the release, go to the same page  [...]
 related to the update have time to surface.</p><h2 
id=4-investigate-performance-regressions>4. Investigate performance 
regressions</h2><p>Check the Beam load tests for possible performance 
regressions.
-Measurements are available on <a 
href=http://metrics.beam.apache.org>metrics.beam.apache.org</a>.</p><p>All 
Runners which publish data should be checked for the following, in both 
<em>batch</em> and <em>streaming</em> mode:</p><ul><li><a 
href=http://metrics.beam.apache.org/d/MOi-kf3Zk/pardo-load-tests>ParDo</a> and 
<a href=http://metrics.beam.apache.org/d/UYZ-oJ3Zk/gbk-load-test>GBK</a>: 
Runtime, latency, checkpoint duration</li><li><a 
href=http://metrics.beam.apache.org/d/ahuaA_zGz/nexm [...]
+Measurements are available on <a 
href=http://metrics.beam.apache.org>metrics.beam.apache.org</a>.</p><p>All 
Runners which publish data should be checked for the following, in both 
<em>batch</em> and <em>streaming</em> mode:</p><ul><li><a 
href=http://metrics.beam.apache.org/d/MOi-kf3Zk/pardo-load-tests>ParDo</a> and 
<a href=http://metrics.beam.apache.org/d/UYZ-oJ3Zk/gbk-load-test>GBK</a>: 
Runtime, latency, checkpoint duration</li><li><a 
href=http://metrics.beam.apache.org/d/ahudA_zGz/nexm [...]
 The role of the release manager is to file JIRA issues for each regression 
with the &lsquo;Fix Version&rsquo; set to the to-be-released version.
 The release manager oversees these just like any other JIRA issue marked with 
the &lsquo;Fix Version&rsquo; of the release.</p><p>The mailing list should be 
informed to allow fixing the regressions in the course of the release.</p><h2 
id=5-create-a-release-branch-in-apachebeam-repository>5. Create a release 
branch in apache/beam repository</h2><p>Attention: Only committer has 
permission to create release branch in apache/beam.</p><p>Release candidates 
are built from a release branch.
 As a final step in preparation for the release, you should create the release 
branch, push it to the Apache code repository, and update version information 
on the original branch.
@@ -409,7 +409,7 @@ If you end up getting permissions errors ask on the mailing 
list for assistance.
 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/12/29</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 
2022/02/11</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 1585110..ddd6dfb 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.36.0/</loc><lastmod>2022-02-07T18:04:31-08:00</lastmod></url><url><loc>/categories/blog/</loc><lastmod>2022-02-09T12:39:16-08:00</lastmod></url><url><loc>/blog/</loc><lastmod>2022-02-09T12:39:16-08:00</lastmod></url><url><loc>/categories/</loc><lastmod>2022-02-09T12:39:16-08:00</lastmod></url><url><loc>/blog/b
 [...]
\ 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.36.0/</loc><lastmod>2022-02-07T18:04:31-08:00</lastmod></url><url><loc>/categories/blog/</loc><lastmod>2022-02-09T12:39:16-08:00</lastmod></url><url><loc>/blog/</loc><lastmod>2022-02-09T12:39:16-08:00</lastmod></url><url><loc>/categories/</loc><lastmod>2022-02-09T12:39:16-08:00</lastmod></url><url><loc>/blog/b
 [...]
\ No newline at end of file

Reply via email to