[maven-site] branch master updated: [MPOM-205] updated release documentation for sha512

[hb...@apache.org]

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

hboutemy pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-site.git


The following commit(s) were added to refs/heads/master by this push:
     new 6e729fe  [MPOM-205] updated release documentation for sha512
6e729fe is described below

commit 6e729fecc30c33ef09c30c7cd8a2f160e6682585
Author: Hervé Boutemy <hb...@apache.org>
AuthorDate: Mon Sep 3 21:34:43 2018 +0200

    [MPOM-205] updated release documentation for sha512
---
 .../release/maven-project-release-procedure.apt         | 17 +++++++++++------
 1 file changed, 11 insertions(+), 6 deletions(-)

diff --git a/content/apt/developers/release/maven-project-release-procedure.apt b/content/apt/developers/release/maven-project-release-procedure.apt
index 7dabba0..cef7059 100644
--- a/content/apt/developers/release/maven-project-release-procedure.apt
+++ b/content/apt/developers/release/maven-project-release-procedure.apt
@@ -161,10 +161,15 @@ I will promote the artifacts to the central repo.
 
 * Copy the source release to the Apache Distribution Area
 
-  The official Apache release is the 'source-release' bundle. All releases must be copied to {{{https://www.apache.org/dist/maven/}the official 
-  release area}}. The release area is maintained with svnsubpub. To deliver a release, you add it to 
-  {{{https://dist.apache.org/repos/dist/release/maven}the subversion repository for the dist area}}: add the release, its signature, and corresponding
-  sha1 files. Currently this requires to be in maven-pmc group (see {{{https://issues.apache.org/jira/browse/INFRA-5945}https://issues.apache.org/jira/browse/INFRA-5945}}).
+  The official Apache release is the 'source-release' bundle distributed in <<<www.apache.org/dist>>>,
+  as described in {{{http://www.apache.org/dev/release-distribution}Apache release distribution policy}}.
+  All releases for Maven must be copied to {{{https://www.apache.org/dist/maven/}the official Maven release area}}.
+  
+  The release area is maintained with svnsubpub. To deliver a release, you add it to 
+  {{{https://dist.apache.org/repos/dist/release/maven}the subversion repository for the dist area}}:
+  add the release, its signature and sha512 checksum files, copying them from
+  <<<target/checkout/target/>>> directory created during <<<mvn release:perform>>> step.
+  Currently this requires to be in maven-pmc group (see {{{https://issues.apache.org/jira/browse/INFRA-5945}https://issues.apache.org/jira/browse/INFRA-5945}}).
   If you are not PMC member, drop a line to <pr...@maven.apache.org> and ask them to do this step for you.
 
   For example:
@@ -172,10 +177,10 @@ I will promote the artifacts to the central repo.
 +--------+
 wagon/wagon-2.2-source-release.zip
 wagon/wagon-2.2-source-release.zip.asc
-wagon/wagon-2.2-source-release.zip.sha1
+wagon/wagon-2.2-source-release.zip.sha512
 +--------+
 
-  You should also run 'svn rm' as needed to clear out older releases.  As per {{{https://www.apache.org/dev/release.html#where-do-releases-go}the policy}},
+  You should also run 'svn rm' as needed to clear out older releases.  As per {{{https://www.apache.org/dev/release.html#where-do-releases-go}the release policy}},
   only the latest release on a branch should stay in the main dist areas. So long as the previous release is at least a day old, the automatic archiver
   will have copied it to the archive.