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 e64d633  Publishing website 2020/06/03 06:03:02 at commit 804dd5e
e64d633 is described below

commit e64d633915730cd89f58140733c1afb301888c95
Author: jenkins <[email protected]>
AuthorDate: Wed Jun 3 06:03:02 2020 +0000

    Publishing website 2020/06/03 06:03:02 at commit 804dd5e
---
 website/generated-content/contribute/index.xml                | 10 +++++++++-
 website/generated-content/contribute/release-guide/index.html |  4 ++--
 website/generated-content/sitemap.xml                         |  2 +-
 3 files changed, 12 insertions(+), 4 deletions(-)

diff --git a/website/generated-content/contribute/index.xml 
b/website/generated-content/contribute/index.xml
index 3be532d..9495141 100644
--- a/website/generated-content/contribute/index.xml
+++ b/website/generated-content/contribute/index.xml
@@ -1377,8 +1377,16 @@ All wheels should be published, in addition to the zip 
of the release source.
 &lt;p>Create and push a new signed tag for the released version by copying the 
tag for the final release candidate, as follows:&lt;/p>
 &lt;pre>&lt;code>VERSION_TAG=&amp;quot;v${RELEASE}&amp;quot;
 git tag -s &amp;quot;$VERSION_TAG&amp;quot; &amp;quot;$RC_TAG&amp;quot;
-git push github &amp;quot;$VERSION_TAG&amp;quot;
+git push upstream &amp;quot;$VERSION_TAG&amp;quot;
 &lt;/code>&lt;/pre>
+&lt;p>After the tag is uploaded, publish the release in the Github UI.&lt;/p>
+&lt;ol>
+&lt;li>Navigate to 
&lt;code>https://github.com/apache/beam/releases/tag/$VERSION_TAG&lt;/code>.&lt;/li>
+&lt;li>Click the &amp;ldquo;Edit tag&amp;rdquo; button.&lt;/li>
+&lt;li>Give the release a title, such as &lt;code>Beam 
2.21.0&lt;/code>.&lt;/li>
+&lt;li>For the release description, copy the current version&amp;rsquo;s 
changes from &lt;code>CHANGES.md&lt;/code>. (You may want to touch up the 
formatting a bit.)&lt;/li>
+&lt;li>Click the &amp;ldquo;Publish release&amp;rdquo; button.&lt;/li>
+&lt;/ol>
 &lt;h3 id="merge-website-pull-request">Merge website pull request&lt;/h3>
 &lt;p>Merge the website pull request to &lt;a 
href="/get-started/downloads/">list the release&lt;/a>, publish the &lt;a 
href="https://beam.apache.org/releases/pydoc/";>Python API reference 
manual&lt;/a>, the &lt;a href="https://beam.apache.org/releases/javadoc/";>Java 
API reference manual&lt;/a> and Blogpost created earlier.&lt;/p>
 &lt;h3 id="mark-the-version-as-released-in-jira">Mark the version as released 
in JIRA&lt;/h3>
diff --git a/website/generated-content/contribute/release-guide/index.html 
b/website/generated-content/contribute/release-guide/index.html
index ccec0eb..722506f 100644
--- a/website/generated-content/contribute/release-guide/index.html
+++ b/website/generated-content/contribute/release-guide/index.html
@@ -358,8 +358,8 @@ All wheels should be published, in addition to the zip of 
the release source.
 (Signatures and hashes do <em>not</em> need to be uploaded.)</li></ul><h3 
id=deploy-source-release-to-distapacheorg>Deploy source release to 
dist.apache.org</h3><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>Move last release 
artifacts from <code>dist.apache.org</code> to <code>archive.apache.org</code> 
using Subversion. Make sure to change these links on the website (<a href=h 
[...]
 </code></pre><p>Verify that:</p><ul><li>Images are published at <a 
href="https://hub.docker.com/search?q=apache%2Fbeam&type=image";>DockerHub</a> 
with tags {RELEASE} and <em>latest</em>.</li><li>Images with <em>latest</em> 
tag are pointing to current release by confirming<ol><li>Digest of the image 
with <em>latest</em> tag is the same as the one with {RELEASE} 
tag.</li></ol></li></ul><h3 id=git-tag>Git tag</h3><p>Create and push a new 
signed tag for the released version by copying the tag [...]
 git tag -s &quot;$VERSION_TAG&quot; &quot;$RC_TAG&quot;
-git push github &quot;$VERSION_TAG&quot;
-</code></pre><h3 id=merge-website-pull-request>Merge website pull 
request</h3><p>Merge the website pull request to <a 
href=/get-started/downloads/>list the release</a>, publish the <a 
href=https://beam.apache.org/releases/pydoc/>Python API reference manual</a>, 
the <a href=https://beam.apache.org/releases/javadoc/>Java API reference 
manual</a> and Blogpost created earlier.</p><h3 
id=mark-the-version-as-released-in-jira>Mark the version as released in 
JIRA</h3><p>In JIRA, inside <a href=h [...]
+git push upstream &quot;$VERSION_TAG&quot;
+</code></pre><p>After the tag is uploaded, publish the release in the Github 
UI.</p><ol><li>Navigate to 
<code>https://github.com/apache/beam/releases/tag/$VERSION_TAG</code>.</li><li>Click
 the &ldquo;Edit tag&rdquo; button.</li><li>Give the release a title, such as 
<code>Beam 2.21.0</code>.</li><li>For the release description, copy the current 
version&rsquo;s changes from <code>CHANGES.md</code>. (You may want to touch up 
the formatting a bit.)</li><li>Click the &ldquo;Publish release&rd [...]
 <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. 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.< [...]
 <a href=http://www.apache.org>The Apache Software Foundation</a>
 | <a href=/privacy_policy>Privacy Policy</a>
diff --git a/website/generated-content/sitemap.xml 
b/website/generated-content/sitemap.xml
index 21d9754..122fbe7 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-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
+<?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

Reply via email to