[maven-site] branch master updated: [MPOM-205] added more details on how a PMC can publish for a non-PMC

[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 503b052  [MPOM-205] added more details on how a PMC can publish for a non-PMC
503b052 is described below

commit 503b052adbee76e2e3cb94b1572fc17955de68e9
Author: Hervé Boutemy <hb...@apache.org>
AuthorDate: Mon Sep 3 21:37:50 2018 +0200

    [MPOM-205] added more details on how a PMC can publish for a non-PMC
---
 content/apt/developers/release/maven-project-release-procedure.apt | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/content/apt/developers/release/maven-project-release-procedure.apt b/content/apt/developers/release/maven-project-release-procedure.apt
index cef7059..94e2d7c 100644
--- a/content/apt/developers/release/maven-project-release-procedure.apt
+++ b/content/apt/developers/release/maven-project-release-procedure.apt
@@ -170,7 +170,8 @@ I will promote the artifacts to the central repo.
   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.
+  If you are not PMC member, drop a line to <pr...@maven.apache.org> and ask them to do this step for you: the PMC member will
+  get the source release bundle and its signature from Nexus staging repository and will create sha512 checksum file by hand.
 
   For example: