svn commit: r1866353 - in /maven/website/content: developers/release/maven-core-release.html maven-site-1.0-site.jar

[svn-site-role]

Author: svn-site-role
Date: Wed Sep  4 05:48:03 2019
New Revision: 1866353

Log:
Site checkin for project Apache Maven Site

Modified:
    maven/website/content/developers/release/maven-core-release.html
    maven/website/content/maven-site-1.0-site.jar

Modified: maven/website/content/developers/release/maven-core-release.html
==============================================================================
--- maven/website/content/developers/release/maven-core-release.html (original)
+++ maven/website/content/developers/release/maven-core-release.html Wed Sep  4 
05:48:03 2019
@@ -143,7 +143,7 @@
 <ul>
 
 <li><a class="externalLink" 
href="https://dist.apache.org/repos/dist/release/maven/maven-3/";>https://dist.apache.org/repos/dist/release/maven/maven-3/</a>$VERSION/binaries</li>
-<li><a class="externalLink" 
href="https://dist.apache.org/repos/dist/release/maven/maven-3/";>https://dist.apache.org/repos/dist/release/maven/maven-3/</a>$VERSION/source</li>
+<li><a class="externalLink" 
href="https://dist.apache.org/repos/dist/release/maven/maven-3/";>https://dist.apache.org/repos/dist/release/maven/maven-3/</a>$VERSION/source
 (notice: singular&#x2026;)</li>
 </ul>
 <p>Note that the policy for failed releases is to move forward with a new 
version. The tag that produced the failed released is left in place for 
posterity. So if the release of, say, 3.2.4 fails then we move forward with 
3.2.5.</p><section>
 <h3><a name="Produce_Release_Candidates"></a>Produce Release Candidates</h3>

Modified: maven/website/content/maven-site-1.0-site.jar
==============================================================================
Binary files - no diff available.