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 9dc8dc6 Update release process (#341)
9dc8dc6 is described below
commit 9dc8dc6670e1313d2925b30eb5e7cf6d03a70e68
Author: Liang-Chi Hsieh <vii...@gmail.com>
AuthorDate: Mon May 17 16:18:24 2021 -0700
Update release process (#341)
---
release-process.md | 13 -------------
site/release-process.html | 13 -------------
2 files changed, 26 deletions(-)
diff --git a/release-process.md b/release-process.md
index 0e5e5db..72dcdb4 100644
--- a/release-process.md
+++ b/release-process.md
@@ -203,10 +203,6 @@ $ svn rm
https://dist.apache.org/repos/dist/release/spark/spark-1.1.0
You will also need to update `js/download.js` to indicate the release is not
mirrored
anymore, so that the correct links are generated on the site.
-Also take a moment to check `HiveExternalCatalogVersionsSuite.scala` starting
with branch-2.2
-and see if it needs to be adjusted, since that test relies on mirrored
downloads of previous
-releases.
-
<h4>Update the Spark Apache Repository</h4>
@@ -317,15 +313,6 @@ $ git shortlog v1.1.1 --grep "$EXPR" > contrib.txt
$ git log v1.1.1 --grep "$expr" --shortstat --oneline | grep -B 1 -e
"[3-9][0-9][0-9] insert" -e "[1-9][1-9][1-9][1-9] insert" | grep SPARK >
large-patches.txt
```
-<h4>Update `HiveExternalCatalogVersionsSuite`</h4>
-
-When a new release occurs, `PROCESS_TABLES.testingVersions` in
`HiveExternalCatalogVersionsSuite`
-must be updated shortly thereafter. This list should contain the latest
release in all active
-maintenance branches, and no more.
-For example, as of this writing, it has value `val testingVersions =
Seq("2.1.3", "2.2.2", "2.3.2")`.
-"2.4.0" will be added to the list when it's released. "2.1.3" will be removed
(and removed from the Spark dist mirrors)
-when the branch is no longer maintained. "2.3.2" will become "2.3.3" when
"2.3.3" is released.
-
<h4>Create an Announcement</h4>
Once everything is working (website docs, website changes) create an
announcement on the website
diff --git a/site/release-process.html b/site/release-process.html
index 860abec..87acebe 100644
--- a/site/release-process.html
+++ b/site/release-process.html
@@ -398,10 +398,6 @@ To delete older versions simply use svn rm:</p>
<p>You will also need to update <code class="language-plaintext
highlighter-rouge">js/download.js</code> to indicate the release is not mirrored
anymore, so that the correct links are generated on the site.</p>
-<p>Also take a moment to check <code class="language-plaintext
highlighter-rouge">HiveExternalCatalogVersionsSuite.scala</code> starting with
branch-2.2
-and see if it needs to be adjusted, since that test relies on mirrored
downloads of previous
-releases.</p>
-
<h4>Update the Spark Apache Repository</h4>
<p>Check out the tagged commit for the release candidate that passed and apply
the correct version tag.</p>
@@ -508,15 +504,6 @@ $ git shortlog v1.1.1 --grep "$EXPR" > contrib.txt
$ git log v1.1.1 --grep "$expr" --shortstat --oneline | grep -B 1 -e
"[3-9][0-9][0-9] insert" -e "[1-9][1-9][1-9][1-9] insert" | grep SPARK >
large-patches.txt
</code></pre></div></div>
-<h4>Update `HiveExternalCatalogVersionsSuite`</h4>
-
-<p>When a new release occurs, <code class="language-plaintext
highlighter-rouge">PROCESS_TABLES.testingVersions</code> in <code
class="language-plaintext
highlighter-rouge">HiveExternalCatalogVersionsSuite</code>
-must be updated shortly thereafter. This list should contain the latest
release in all active
-maintenance branches, and no more.
-For example, as of this writing, it has value <code class="language-plaintext
highlighter-rouge">val testingVersions = Seq("2.1.3", "2.2.2", "2.3.2")</code>.
-“2.4.0” will be added to the list when it’s released.
“2.1.3” will be removed (and removed from the Spark dist mirrors)
-when the branch is no longer maintained. “2.3.2” will become
“2.3.3” when “2.3.3” is released.</p>
-
<h4>Create an Announcement</h4>
<p>Once everything is working (website docs, website changes) create an
announcement on the website
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@spark.apache.org
For additional commands, e-mail: commits-h...@spark.apache.org
