You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by gi...@apache.org on 2020/06/16 06:02:07 UTC
[beam] branch asf-site updated: Publishing website 2020/06/16
06:01:53 at commit 232c878
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 995fd1f Publishing website 2020/06/16 06:01:53 at commit 232c878
995fd1f is described below
commit 995fd1f040d5e0ba609bb49dbb810dadee2a7d7a
Author: jenkins <us...@infra.apache.org>
AuthorDate: Tue Jun 16 06:01:53 2020 +0000
Publishing website 2020/06/16 06:01:53 at commit 232c878
---
website/generated-content/contribute/index.xml | 21 ++++++++++++---------
.../contribute/release-guide/index.html | 6 +++---
2 files changed, 15 insertions(+), 12 deletions(-)
diff --git a/website/generated-content/contribute/index.xml b/website/generated-content/contribute/index.xml
index e42cb0e..e4c42c1 100644
--- a/website/generated-content/contribute/index.xml
+++ b/website/generated-content/contribute/index.xml
@@ -307,12 +307,16 @@ limitations under the License.
<ul>
<li><a href="#deploy-artifacts-to-maven-central-repository">Deploy artifacts to Maven Central Repository</a></li>
<li><a href="#deploy-python-artifacts-to-pypi">Deploy Python artifacts to PyPI</a></li>
-<li><a href="#deploy-source-release-to-distapacheorg">Deploy source release to dist.apache.org</a></li>
<li><a href="#deploy-sdk-docker-images-to-dockerhub">Deploy SDK docker images to DockerHub</a></li>
<li><a href="#merge-website-pull-requests">Merge Website pull requests</a></li>
<li><a href="#git-tag">Git tag</a></li>
+<li><a href="#pmc-only-finalization">PMC-Only Finalization</a>
+<ul>
+<li><a href="#deploy-source-release-to-distapacheorg">Deploy source release to dist.apache.org</a></li>
<li><a href="#mark-the-version-as-released-in-jira">Mark the version as released in JIRA</a></li>
<li><a href="#recordkeeping-with-asf">Recordkeeping with ASF</a></li>
+</ul>
+</li>
<li><a href="#checklist-to-proceed-to-the-next-step-3">Checklist to proceed to the next step</a></li>
</ul>
</li>
@@ -1354,10 +1358,6 @@ please follow <a href="https://help.github.com/articles/creating-a-personal-a
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="https://github.com/apache/beam/pull/11727">example</a>).</p>
-<p><strong>NOTE</strong>: Only PMC members have permissions to do it, ping <a href="mailto:dev@beam.apache.org">dev@</a> for assitance;</p>
<h3 id="deploy-sdk-docker-images-to-dockerhub">Deploy SDK docker images to DockerHub</h3>
<ul>
<li>Script: <a href="https://github.com/apache/beam/blob/master/release/src/main/scripts/publish_docker_images.sh">publish_docker_images.sh</a></li>
@@ -1388,12 +1388,15 @@ git push https://github.com/apache/beam &quot;$VERSION_TAG&quot;
</code></pre><p>After the tag is uploaded, publish the release notes to Github, as follows:</p>
<pre><code>cd beam/release/src/main/scripts &amp;&amp; ./publish_github_release_notes.sh
</code></pre><p>Note this script reads the release notes from the blog post, so you should make sure to run this from master <em>after</em> merging the blog post PR.</p>
-<h3 id="mark-the-version-as-released-in-jira">Mark the version as released in JIRA</h3>
+<h3 id="pmc-only-finalization">PMC-Only Finalization</h3>
+<p>There are a few release finalization tasks that only PMC members have permissions to do. Ping <a href="mailto:dev@beam.apache.org">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&rsquo;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 change these links on the website (<a href="https://github.com/apache/beam/pull/11727">e [...]
+<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>
-<p><strong>NOTE</strong>: Only PMC members have permissions to do it, ping <a href="mailto:dev@beam.apache.org">dev@</a> for assitance;</p>
-<h3 id="recordkeeping-with-asf">Recordkeeping with ASF</h3>
+<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><strong>NOTE</strong>: Only PMC members have permissions to do it, ping <a href="mailto:dev@beam.apache.org">dev@</a> for assitance;</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>
diff --git a/website/generated-content/contribute/release-guide/index.html b/website/generated-content/contribute/release-guide/index.html
index a12462c..7bf9d1d 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> [...]
@@ -355,12 +355,12 @@ mvn compile exec:java -Dexec.mainClass=org.apache.beam.examples.complete.game.in
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=deploy-python-artifacts-to-pypi>Deploy Python artifacts to PyPI</h3><ul><li>Script: <a href=https://github.com/apache/beam/blob/master/release/src/main/scripts/deploy_pypi.sh>deploy_pypi.sh</a></li><li>Usage</li></ul><pre><code>./beam/release/src/main/scripts/deploy_pypi.sh
</code></pre><ul><li>Verify that the files at <a href=https://pypi.org/project/apache-beam/#files>https://pypi.org/project/apache-beam/#files</a> are correct.
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 [...]
+(Signatures and hashes do <em>not</em> need to be uploaded.)</li></ul><h3 id=deploy-sdk-docker-images-to-dockerhub>Deploy SDK docker images to DockerHub</h3><ul><li>Script: <a href=https://github.com/apache/beam/blob/master/release/src/main/scripts/publish_docker_images.sh>publish_docker_images.sh</a></li><li>Usage</li></ul><pre><code>./beam/release/src/main/scripts/publish_docker_images.sh
</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=merge-website-pull-requests>Merge Website pull requests</h3><p>Merge all of the website pull reques [...]
git tag -s "$VERSION_TAG" "$RC_TAG"
git push https://github.com/apache/beam "$VERSION_TAG"
</code></pre><p>After the tag is uploaded, publish the release notes to Github, as follows:</p><pre><code>cd beam/release/src/main/scripts && ./publish_github_release_notes.sh
-</code></pre><p>Note this script reads the release notes from the blog post, so you should make sure to run this from master <em>after</em> merging the blog post PR.</p><h3 id=mark-the-version-as-released-in-jira>Mark the version as released in JIRA</h3><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 [...]
+</code></pre><p>Note this script reads the release notes from the blog post, so you should make sure to run this from master <em>after</em> merging the blog post PR.</p><h3 id=pmc-only-finalization>PMC-Only Finalization</h3><p>There are a few release finalization tasks that only PMC members have permissions to do. Ping <a href=mailto:dev@beam.apache.org>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 [...]
<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>