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 9a9f838 Publishing website 2019/04/25 21:47:37 at commit b529db9
9a9f838 is described below
commit 9a9f8381d0d4c11356b72c63d3bf4b68c4439f37
Author: jenkins <bui...@apache.org>
AuthorDate: Thu Apr 25 21:47:37 2019 +0000
Publishing website 2019/04/25 21:47:37 at commit b529db9
---
.../contribute/release-guide/index.html | 37 ++++++++++++----------
1 file changed, 21 insertions(+), 16 deletions(-)
diff --git a/website/generated-content/contribute/release-guide/index.html
b/website/generated-content/contribute/release-guide/index.html
index 9f34de3..0fae700f 100644
--- a/website/generated-content/contribute/release-guide/index.html
+++ b/website/generated-content/contribute/release-guide/index.html
@@ -227,6 +227,7 @@
<ul>
<li><a href="#run-build_release_candidatesh-to-create-rc">Run
build_release_candidate.sh to create RC</a></li>
<li><a href="#run-all-steps-manually-1">Run all steps manually</a></li>
+ <li><a href="#write-the-beam-blog-post-and-create-a-pull-request">Write
the Beam blog post and create a pull request</a></li>
</ul>
</li>
<li><a href="#vote-on-the-release-candidate">Vote on the release
candidate</a>
@@ -254,7 +255,6 @@
<li><a href="#promote-the-release">Promote the release</a>
<ul>
<li><a href="#apache-mailing-lists">Apache mailing lists</a></li>
- <li><a href="#beam-blog">Beam blog</a></li>
<li><a href="#social-media">Social media</a></li>
<li><a href="#checklist-to-declare-the-process-completed">Checklist to
declare the process completed</a></li>
</ul>
@@ -334,6 +334,9 @@ limitations under the License.
<li><a href="#build-the-pydoc-api-reference"
id="markdown-toc-build-the-pydoc-api-reference">Build the Pydoc API
reference</a></li>
<li><a href="#propose-pull-requests-for-website-updates"
id="markdown-toc-propose-pull-requests-for-website-updates">Propose pull
requests for website updates</a></li>
<li><a href="#build-and-stage-python-wheels"
id="markdown-toc-build-and-stage-python-wheels">Build and stage python
wheels</a></li>
+ </ul>
+ </li>
+ <li><a href="#write-the-beam-blog-post-and-create-a-pull-request"
id="markdown-toc-write-the-beam-blog-post-and-create-a-pull-request">Write the
Beam blog post and create a pull request</a> <ul>
<li><a href="#checklist-to-proceed-to-the-next-step-2"
id="markdown-toc-checklist-to-proceed-to-the-next-step-2">Checklist to proceed
to the next step</a></li>
</ul>
</li>
@@ -367,7 +370,6 @@ limitations under the License.
</li>
<li><a href="#promote-the-release"
id="markdown-toc-promote-the-release">Promote the release</a> <ul>
<li><a href="#apache-mailing-lists"
id="markdown-toc-apache-mailing-lists">Apache mailing lists</a></li>
- <li><a href="#beam-blog" id="markdown-toc-beam-blog">Beam blog</a></li>
<li><a href="#social-media" id="markdown-toc-social-media">Social
media</a></li>
<li><a href="#checklist-to-declare-the-process-completed"
id="markdown-toc-checklist-to-declare-the-process-completed">Checklist to
declare the process completed</a></li>
</ul>
@@ -979,8 +981,6 @@ the version number has changed, download a new version of
the corresponding
<p>For this step, we recommend you using automation script to create a RC, but
you still can perform all steps manually if you want.</p>
-<p><em>BUT</em> the final step of rc creation is <code
class="highlighter-rouge">Build and stage python wheels</code>, which need to
done manually.</p>
-
<h3 id="run-build_release_candidatesh-to-create-rc">Run
build_release_candidate.sh to create RC</h3>
<ul>
<li>
@@ -1018,6 +1018,7 @@ When prompted for a description, enter “Apache Beam,
version X, release candid
<li>Add new release into <code
class="highlighter-rouge">website/src/get-started/downloads.md</code>.</li>
<li>Update last release download links in <code
class="highlighter-rouge">website/src/get-started/downloads.md</code>.</li>
<li>Update <code class="highlighter-rouge">website/src/.htaccess</code>
to redirect to the new version.</li>
+ <li>Build and stage python wheels.</li>
</ol>
</li>
</ul>
@@ -1205,6 +1206,12 @@ to point to the new release. See file history for
examples.</li>
<p>Once all python wheels have been staged <a
href="https://dist.apache.org/repos/dist/dev/beam/";>dist.apache.org</a>,
please run <a
href="https://github.com/apache/beam/blob/master/release/src/main/scripts/sign_hash_python_wheels.sh";>./sign_hash_python_wheels.sh</a>
to sign and hash python wheels.</p>
+<h3 id="write-the-beam-blog-post-and-create-a-pull-request">Write the Beam
blog post and create a pull request</h3>
+
+<p>Major or otherwise important releases should have a blog post. Write one if
needed for this particular release. Minor releases that don’t introduce new
major functionality don’t necessarily need to be blogged.</p>
+
+<p><em>Tip:</em> Use git log to find contributors to the releases. (e.g: <code
class="highlighter-rouge">git log --pretty='%aN' ^v2.10.0 v2.11.0 | sort |
uniq</code>).</p>
+
<h4 id="checklist-to-proceed-to-the-next-step-2">Checklist to proceed to the
next step</h4>
<ol>
@@ -1245,21 +1252,25 @@ The complete staging area is available for your review,
which includes:
* the official Apache source release to be deployed to dist.apache.org [2],
which is signed with the key with fingerprint FFFFFFFF [3],
* all artifacts to be deployed to the Maven Central Repository [4],
* source code tag "v1.2.3-RC3" [5],
-* website pull request listing the release and publishing the API reference
manual [6].
+* website pull request listing the release [6], publishing the API reference
manual [7], and the blog post [8].
* Java artifacts were built with Maven MAVEN_VERSION and OpenJDK/Oracle JDK
JDK_VERSION.
* Python artifacts are deployed along with the source release to the
dist.apache.org [2].
+* Validation sheet with a tab for 1.2.3 release to help with validation [9].
The vote will be open for at least 72 hours. It is adopted by majority
approval, with at least 3 PMC affirmative votes.
Thanks,
Release Manager
-[1] link
-[2] link
+[1] https://jira.apache.org/jira/secure/ReleaseNote.jspa?projectId=...
+[2] https://dist.apache.org/repos/dist/dev/beam/1.2.3/
[3] https://dist.apache.org/repos/dist/release/beam/KEYS
-[4] link
-[5] link
-[6] link
+[4] https://repository.apache.org/content/repositories/orgapachebeam-NNNN/
+[5] https://github.com/apache/beam/tree/v1.2.3-RC3
+[6] https://github.com/apache/beam/pull/...
+[7] https://github.com/apache/beam-site/pull/...
+[8] https://github.com/apache/beam/pull/...
+[9]
https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=...
</code></pre>
</div>
@@ -1683,12 +1694,6 @@ git push github "$VERSION_TAG"
<p>Announce the release on the annou...@apache.org mailing list.</p>
-<h3 id="beam-blog">Beam blog</h3>
-
-<p>Major or otherwise important releases should have a blog post. Write one if
needed for this particular release. Minor releases that don’t introduce new
major functionality don’t necessarily need to be blogged.</p>
-
-<p><em>Tip:</em> Use git log to find contributors to the releases. (e.g: <code
class="highlighter-rouge">git log --pretty='%aN' ^v2.10.0 v2.11.0 | sort |
uniq</code>).</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>
