You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@spark.apache.org by sr...@apache.org on 2018/01/16 20:18:00 UTC
spark-website git commit: Note update of master branch SNAPSHOT
versions as part of cutting new release branch
Repository: spark-website
Updated Branches:
refs/heads/asf-site ab2bcbf28 -> b3ecc858f
Note update of master branch SNAPSHOT versions as part of cutting new release branch
Project: http://git-wip-us.apache.org/repos/asf/spark-website/repo
Commit: http://git-wip-us.apache.org/repos/asf/spark-website/commit/b3ecc858
Tree: http://git-wip-us.apache.org/repos/asf/spark-website/tree/b3ecc858
Diff: http://git-wip-us.apache.org/repos/asf/spark-website/diff/b3ecc858
Branch: refs/heads/asf-site
Commit: b3ecc858f3a65f98d860f63eb75099308039cdfa
Parents: ab2bcbf
Author: Sean Owen <so...@cloudera.com>
Authored: Wed Jan 10 09:51:53 2018 -0600
Committer: Sean Owen <so...@cloudera.com>
Committed: Tue Jan 16 14:16:30 2018 -0600
----------------------------------------------------------------------
release-process.md | 9 +++++++--
site/release-process.html | 9 +++++++--
2 files changed, 14 insertions(+), 4 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/spark-website/blob/b3ecc858/release-process.md
----------------------------------------------------------------------
diff --git a/release-process.md b/release-process.md
index 1c030f9..f25a429 100644
--- a/release-process.md
+++ b/release-process.md
@@ -39,8 +39,13 @@ If you are a new Release Manager, you can read up on the process from the follow
The main step towards preparing a release is to create a release branch. This is done via
standard Git branching mechanism and should be announced to the community once the branch is
-created. It is also good to set up Jenkins jobs for the release branch once it is cut to
-ensure tests are passing (consult Josh Rosen and Shane Knapp for help with this).
+created.
+
+It is also good to set up Jenkins jobs for the release branch once it is cut to
+ensure tests are passing. These are jobs like
+https://amplab.cs.berkeley.edu/jenkins/view/Spark%20QA%20Test/job/spark-branch-2.3-test-maven-hadoop-2.7/ .
+Consult Josh Rosen and Shane Knapp for help with this. Also remember to add the newly-added jobs
+to the test dashboard at https://amplab.cs.berkeley.edu/jenkins/view/Spark%20QA%20Test%20(Dashboard)/ .
<h3>Cutting a Release Candidate</h3>
http://git-wip-us.apache.org/repos/asf/spark-website/blob/b3ecc858/site/release-process.html
----------------------------------------------------------------------
diff --git a/site/release-process.html b/site/release-process.html
index e08990f..dc22d9c 100644
--- a/site/release-process.html
+++ b/site/release-process.html
@@ -239,8 +239,13 @@
<p>The main step towards preparing a release is to create a release branch. This is done via
standard Git branching mechanism and should be announced to the community once the branch is
-created. It is also good to set up Jenkins jobs for the release branch once it is cut to
-ensure tests are passing (consult Josh Rosen and Shane Knapp for help with this).</p>
+created.</p>
+
+<p>It is also good to set up Jenkins jobs for the release branch once it is cut to
+ensure tests are passing. These are jobs like
+https://amplab.cs.berkeley.edu/jenkins/view/Spark%20QA%20Test/job/spark-branch-2.3-test-maven-hadoop-2.7/ .
+Consult Josh Rosen and Shane Knapp for help with this. Also remember to add the newly-added jobs
+to the test dashboard at https://amplab.cs.berkeley.edu/jenkins/view/Spark%20QA%20Test%20(Dashboard)/ .</p>
<h3>Cutting a Release Candidate</h3>
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@spark.apache.org
For additional commands, e-mail: commits-help@spark.apache.org