You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@spark.apache.org by gu...@apache.org on 2024/02/26 23:59:04 UTC
(spark-website) branch asf-site updated: Guide release manager to give a last chance to backup docs artifact before removing it
This is an automated email from the ASF dual-hosted git repository.
gurwls223 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 9bac0d4a08 Guide release manager to give a last chance to backup docs artifact before removing it
9bac0d4a08 is described below
commit 9bac0d4a08bce657d19b034d4e3dee46c5ca9789
Author: Jungtaek Lim <ka...@gmail.com>
AuthorDate: Tue Feb 27 08:58:55 2024 +0900
Guide release manager to give a last chance to backup docs artifact before removing it
In release process page, we guide the release manager "too lately" about keeping the generated docs of the latest RC. The guidance sentence appears later than removing docs from svn.
https://spark.apache.org/release-process.html - read through the section "finalize the release".
If release manager does not have any backup, they are expected to build the docs from scratch, and it's really painful to set up languages and corresponding libraries locally to build the doc (release script with docker is no longer usable at this time). It would be better to remind that they can take a backup before removing the artifact, which they will use the backup very soon.
Here is the screenshot of the change - bold NOTE sentence:
<img width="994" alt="스크린샷 2024-02-26 오후 4 33 07" src="https://github.com/apache/spark-website/assets/1317309/949ab008-bb84-4eaf-880f-084ebca3bd90">
Author: Jungtaek Lim <ka...@gmail.com>
Closes #505 from HeartSaVioR/guide-do-backup-docs-artifact-on-release-finalization.
---
release-process.md | 2 ++
site/release-process.html | 2 ++
2 files changed, 4 insertions(+)
diff --git a/release-process.md b/release-process.md
index 3e2a71af3d..f0884d2c41 100644
--- a/release-process.md
+++ b/release-process.md
@@ -254,6 +254,8 @@ Since it requires further manual steps, please also contact the <a href="mailto:
<h4>Remove RC artifacts from repositories</h4>
+**NOTE! If you did not make a backup of docs for approved RC, this is the last time you can make a backup. This will be used to upload the docs to the website in next few step. Check out docs from svn before removing the directory.**
+
After the vote passes and you moved the approved RC to the release repository, you should delete
the RC directories from the staging repository. For example:
diff --git a/site/release-process.html b/site/release-process.html
index e043c55f0f..a523a2497a 100644
--- a/site/release-process.html
+++ b/site/release-process.html
@@ -391,6 +391,8 @@ Since it requires further manual steps, please also contact the <a href="mailto:
<h4>Remove RC artifacts from repositories</h4>
+<p><strong>NOTE! If you did not make a backup of docs for approved RC, this is the last time you can make a backup. This will be used to upload the docs to the website in next few step. Check out docs from svn before removing the directory.</strong></p>
+
<p>After the vote passes and you moved the approved RC to the release repository, you should delete
the RC directories from the staging repository. For example:</p>
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@spark.apache.org
For additional commands, e-mail: commits-help@spark.apache.org