You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by el...@apache.org on 2020/08/24 11:12:44 UTC
[maven-site] 01/01: docs: listing a release requires PMC membership
This is an automated email from the ASF dual-hosted git repository.
elharo pushed a commit to branch elharo-patch-5
in repository https://gitbox.apache.org/repos/asf/maven-site.git
commit f8a0832de91fe703ceefe8ebb6fd383642e60c90
Author: Elliotte Rusty Harold <el...@users.noreply.github.com>
AuthorDate: Mon Aug 24 11:12:34 2020 +0000
docs: listing a release requires PMC membership
@khmarbaise
---
content/apt/developers/release/maven-project-release-procedure.apt | 6 +++++-
1 file changed, 5 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 1f55207..9714002 100644
--- a/content/apt/developers/release/maven-project-release-procedure.apt
+++ b/content/apt/developers/release/maven-project-release-procedure.apt
@@ -172,7 +172,7 @@ 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: the PMC member will
+ If you are not a 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:
@@ -190,8 +190,12 @@ wagon/wagon-2.2-source-release.zip.sha512
To check that everything is ok in the dist area, dist-tool-plugin has been written and run once a day to produce
{{{https://builds.apache.org/view/M-R/view/Maven/job/dist-tool-plugin/site/dist-tool-check-source-release.html}"Disttool> Source Release" report}}.
+* List the release
+
After committing the 3 source-release files, visit {{{https://reporter.apache.org/addrelease.html?maven}Apache Committee Report Helper}} to add your release data with the Full Version Name and Date of Release.
(You will receive an e-mail for it as well).
+
+ If you are not a PMC member, drop a line to <pr...@maven.apache.org> and ask them to do this step for you.
* Promote the release