You are viewing a plain text version of this content. The canonical link for it is here.
Posted to site-commits@maven.apache.org by sv...@apache.org on 2018/09/03 19:38:34 UTC
svn commit: r1839993 - in /maven/website/content:
developers/release/maven-project-release-procedure.html
maven-site-1.0-site.jar
Author: svn-site-role
Date: Mon Sep 3 19:38:33 2018
New Revision: 1839993
Log:
Site checkin for project Apache Maven Site
Modified:
maven/website/content/developers/release/maven-project-release-procedure.html
maven/website/content/maven-site-1.0-site.jar
Modified: maven/website/content/developers/release/maven-project-release-procedure.html
==============================================================================
--- maven/website/content/developers/release/maven-project-release-procedure.html (original)
+++ maven/website/content/developers/release/maven-project-release-procedure.html Mon Sep 3 19:38:33 2018
@@ -233,7 +233,7 @@ I will promote the artifacts to the cent
<div class="section">
<h3><a name="Copy_the_source_release_to_the_Apache_Distribution_Area"></a>Copy the source release to the Apache Distribution Area</h3>
<p>The official Apache release is the 'source-release' bundle distributed in <tt>www.apache.org/dist</tt>, as described in <a class="externalLink" href="http://www.apache.org/dev/release-distribution">Apache release distribution policy</a>. All releases for Maven must be copied to <a class="externalLink" href="https://www.apache.org/dist/maven/">the official Maven release area</a>.</p>
-<p>The release area is maintained with svnsubpub. To deliver a release, you add it to <a class="externalLink" href="https://dist.apache.org/repos/dist/release/maven">the subversion repository for the dist area</a>: add the release, its signature and sha512 checksum files, copying them from <tt>target/checkout/target/</tt> directory created during <tt>mvn release:perform</tt> step. Currently this requires to be in maven-pmc group (see <a class="externalLink" href="https://issues.apache.org/jira/browse/INFRA-5945">https://issues.apache.org/jira/browse/INFRA-5945</a>). If you are not PMC member, drop a line to <i>private@maven.apache.org</i> and ask them to do this step for you.</p>
+<p>The release area is maintained with svnsubpub. To deliver a release, you add it to <a class="externalLink" href="https://dist.apache.org/repos/dist/release/maven">the subversion repository for the dist area</a>: add the release, its signature and sha512 checksum files, copying them from <tt>target/checkout/target/</tt> directory created during <tt>mvn release:perform</tt> step. Currently this requires to be in maven-pmc group (see <a class="externalLink" href="https://issues.apache.org/jira/browse/INFRA-5945">https://issues.apache.org/jira/browse/INFRA-5945</a>). If you are not PMC member, drop a line to <i>private@maven.apache.org</i> 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.</p>
<p>For example:</p>
<div class="source"><pre class="prettyprint linenums">wagon/wagon-2.2-source-release.zip
wagon/wagon-2.2-source-release.zip.asc
Modified: maven/website/content/maven-site-1.0-site.jar
==============================================================================
Binary files - no diff available.