This is an automated email from the ASF dual-hosted git repository.

felixcheung 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 70a6071  add checker note (#168)
70a6071 is described below

commit 70a60716fed85bfcfce4188b26faeb63ecbe2b79
Author: Felix Cheung <felixche...@users.noreply.github.com>
AuthorDate: Sat Jan 12 20:07:14 2019 -0500

    add checker note (#168)
    
    dd note to check checker after release
---
 release-process.md        | 4 ++--
 site/release-process.html | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/release-process.md b/release-process.md
index 14c9c16..31d395c 100644
--- a/release-process.md
+++ b/release-process.md
@@ -130,7 +130,7 @@ that looks something like `[RESULT] [VOTE]...`.
 **THIS STEP IS IRREVERSIBLE so make sure you selected the correct staging 
repository. Once you
 move the artifacts into the release folder, they cannot be removed.**
 
-After the vote passes, to upload the binaries to Apache mirrors, you move the 
binaries from dev directory (this should be where they are voted) to release 
directory. This "moving" is the only way you can add stuff to the actual 
release directory.
+After the vote passes, to upload the binaries to Apache mirrors, you move the 
binaries from dev directory (this should be where they are voted) to release 
directory. This "moving" is the only way you can add stuff to the actual 
release directory. (Note: only PMC can move to release directory)
 
 ```
 # Move the sub-directory in "dev" to the
@@ -146,7 +146,7 @@ curl "https://dist.apache.org/repos/dist/dev/spark/KEYS"; > 
svn-spark/KEYS
 
 Verify that the resources are present in <a 
href="https://www.apache.org/dist/spark/";>https://www.apache.org/dist/spark/</a>.
 It may take a while for them to be visible. This will be mirrored throughout 
the Apache network.
-There are a few remaining steps.
+Check the release checker result of the release at <a 
href="https://checker.apache.org/projs/spark.html";>https://checker.apache.org/projs/spark.html</a>.
 
 
 For Maven Central Repository, you can Release from the <a 
href="https://repository.apache.org/";>Apache Nexus Repository Manager</a>. This 
is already populated by the `release-build.sh publish-release` step. Log in, 
open Staging Repositories, find the one voted on (eg. orgapachespark-1257 for 
https://repository.apache.org/content/repositories/orgapachespark-1257/), 
select and click Release and confirm. If successful, it should show up under 
https://repository.apache.org/content/repositori [...]
diff --git a/site/release-process.html b/site/release-process.html
index 2a4b82b..65f8fb4 100644
--- a/site/release-process.html
+++ b/site/release-process.html
@@ -334,7 +334,7 @@ that looks something like <code>[RESULT] 
[VOTE]...</code>.</p>
 <p><strong>THIS STEP IS IRREVERSIBLE so make sure you selected the correct 
staging repository. Once you
 move the artifacts into the release folder, they cannot be 
removed.</strong></p>
 
-<p>After the vote passes, to upload the binaries to Apache mirrors, you move 
the binaries from dev directory (this should be where they are voted) to 
release directory. This &#8220;moving&#8221; is the only way you can add stuff 
to the actual release directory.</p>
+<p>After the vote passes, to upload the binaries to Apache mirrors, you move 
the binaries from dev directory (this should be where they are voted) to 
release directory. This &#8220;moving&#8221; is the only way you can add stuff 
to the actual release directory. (Note: only PMC can move to release 
directory)</p>
 
 <pre><code># Move the sub-directory in "dev" to the
 # corresponding directory in "release"
@@ -349,7 +349,7 @@ curl "https://dist.apache.org/repos/dist/dev/spark/KEYS"; 
&gt; svn-spark/KEYS
 
 <p>Verify that the resources are present in <a 
href="https://www.apache.org/dist/spark/";>https://www.apache.org/dist/spark/</a>.
 It may take a while for them to be visible. This will be mirrored throughout 
the Apache network.
-There are a few remaining steps.</p>
+Check the release checker result of the release at <a 
href="https://checker.apache.org/projs/spark.html";>https://checker.apache.org/projs/spark.html</a>.</p>
 
 <p>For Maven Central Repository, you can Release from the <a 
href="https://repository.apache.org/";>Apache Nexus Repository Manager</a>. This 
is already populated by the <code>release-build.sh publish-release</code> step. 
Log in, open Staging Repositories, find the one voted on (eg. 
orgapachespark-1257 for 
https://repository.apache.org/content/repositories/orgapachespark-1257/), 
select and click Release and confirm. If successful, it should show up under 
https://repository.apache.org/cont [...]
 and the same under 
https://repository.apache.org/content/groups/maven-staging-group/org/apache/spark/spark-core_2.11/2.2.1/
 (look for the correct release version). After some time this will be 
sync&#8217;d to <a href="https://search.maven.org/";>Maven Central</a> 
automatically.</p>


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@spark.apache.org
For additional commands, e-mail: commits-h...@spark.apache.org

Reply via email to