You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@spark.apache.org by do...@apache.org on 2022/09/20 05:08:14 UTC
[spark-website] branch asf-site updated: Update the Spark Docker container release process (#413)
This is an automated email from the ASF dual-hosted git repository.
dongjoon pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/spark-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 613ad7ac8 Update the Spark Docker container release process (#413)
613ad7ac8 is described below
commit 613ad7ac8b42b7ef9a2214283efcd13c497f11bc
Author: Yuming Wang <yu...@ebay.com>
AuthorDate: Tue Sep 20 13:08:09 2022 +0800
Update the Spark Docker container release process (#413)
---
release-process.md | 11 +++++------
site/release-process.html | 9 ++++-----
2 files changed, 9 insertions(+), 11 deletions(-)
diff --git a/release-process.md b/release-process.md
index e8bba053f..3f6305984 100644
--- a/release-process.md
+++ b/release-process.md
@@ -35,9 +35,6 @@ If you are a new Release Manager, you can read up on the process from the follow
- gpg for signing https://www.apache.org/dev/openpgp.html
- svn https://www.apache.org/dev/version-control.html#https-svn
-
-You should also get access to the ASF Dockerhub. You can get access by filing a INFRA JIRA ticket (see an example ticket https://issues.apache.org/jira/browse/INFRA-21282 ).
-
<h3>Preparing gpg key</h3>
You can skip this section if you have already uploaded your key.
@@ -178,11 +175,10 @@ To cut a release candidate, there are 4 steps:
1. Package the release binaries & sources, and upload them to the Apache staging SVN repo.
1. Create the release docs, and upload them to the Apache staging SVN repo.
1. Publish a snapshot to the Apache staging Maven repo.
-1. Create a RC docker image tag (e.g. `3.4.0-rc1`)
-The process of cutting a release candidate has been mostly automated via the `dev/create-release/do-release-docker.sh` script.
+The process of cutting a release candidate has been automated via the `dev/create-release/do-release-docker.sh` script.
Run this script, type information it requires, and wait until it finishes. You can also do a single step via the `-s` option.
-Please run `do-release-docker.sh -h` and see more details. It does not currently generate the RC docker image tag.
+Please run `do-release-docker.sh -h` and see more details.
<h3>Call a vote on the release candidate</h3>
@@ -393,6 +389,9 @@ $ git log v1.1.1 --grep "$expr" --shortstat --oneline | grep -B 1 -e "[3-9][0-9]
<h4>Create and upload Spark Docker Images</h4>
+Please contact <a href="mailto:holden@apache.org">Holden Karau</a>, <a href="mailto:gengliang@apache.org">Gengliang Wang</a> or <a href="mailto:dongjoon@apache.org">Dongjoon Hyun</a> to do this step because of the [ASF has a limited number of Docker Hub seats](https://infra.apache.org/docker-hub-policy.html).
+
+
The Spark docker images are created using the `./bin/docker-image-tool.sh` that is included in the release artifacts.
diff --git a/site/release-process.html b/site/release-process.html
index dbecf8ff3..1d97d0a26 100644
--- a/site/release-process.html
+++ b/site/release-process.html
@@ -163,8 +163,6 @@
<li>svn https://www.apache.org/dev/version-control.html#https-svn</li>
</ul>
-<p>You should also get access to the ASF Dockerhub. You can get access by filing a INFRA JIRA ticket (see an example ticket https://issues.apache.org/jira/browse/INFRA-21282 ).</p>
-
<h3>Preparing gpg key</h3>
<p>You can skip this section if you have already uploaded your key.</p>
@@ -297,12 +295,11 @@ Note that not all permutations are run on PR therefore it is important to check
<li>Package the release binaries & sources, and upload them to the Apache staging SVN repo.</li>
<li>Create the release docs, and upload them to the Apache staging SVN repo.</li>
<li>Publish a snapshot to the Apache staging Maven repo.</li>
- <li>Create a RC docker image tag (e.g. <code class="language-plaintext highlighter-rouge">3.4.0-rc1</code>)</li>
</ol>
-<p>The process of cutting a release candidate has been mostly automated via the <code class="language-plaintext highlighter-rouge">dev/create-release/do-release-docker.sh</code> script.
+<p>The process of cutting a release candidate has been automated via the <code class="language-plaintext highlighter-rouge">dev/create-release/do-release-docker.sh</code> script.
Run this script, type information it requires, and wait until it finishes. You can also do a single step via the <code class="language-plaintext highlighter-rouge">-s</code> option.
-Please run <code class="language-plaintext highlighter-rouge">do-release-docker.sh -h</code> and see more details. It does not currently generate the RC docker image tag.</p>
+Please run <code class="language-plaintext highlighter-rouge">do-release-docker.sh -h</code> and see more details.</p>
<h3>Call a vote on the release candidate</h3>
@@ -502,6 +499,8 @@ $ git log v1.1.1 --grep "$expr" --shortstat --oneline | grep -B 1 -e "[3-9][0-9]
<h4>Create and upload Spark Docker Images</h4>
+<p>Please contact <a href="mailto:holden@apache.org">Holden Karau</a>, <a href="mailto:gengliang@apache.org">Gengliang Wang</a> or <a href="mailto:dongjoon@apache.org">Dongjoon Hyun</a> to do this step because of the <a href="https://infra.apache.org/docker-hub-policy.html">ASF has a limited number of Docker Hub seats</a>.</p>
+
<p>The Spark docker images are created using the <code class="language-plaintext highlighter-rouge">./bin/docker-image-tool.sh</code> that is included in the release artifacts.</p>
<p>You should install <code class="language-plaintext highlighter-rouge">docker buildx</code> so that you can cross-compile for multiple archs as ARM is becoming increasing popular. If you have access to both an ARM and an x86 machine you should set up a <a href="https://scalingpythonml.com/2020/12/11/some-sharp-corners-with-docker-buildx.html">remote builder as described here</a>, but if you only have one <a href="https://docs.docker.com/buildx/working-with-buildx/">docker buildx with Q [...]
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@spark.apache.org
For additional commands, e-mail: commits-help@spark.apache.org