Author: svn-site-role Date: Sat Mar 27 16:09:35 2021 New Revision: 1888115 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 Sat Mar 27 16:09:35 2021 @@ -157,13 +157,28 @@ under the License. --> Maven differs slightly in its release process due to several extra steps. -<p>The goal is to commit candidate release to svn <code>dev</code> tree <a class="externalLink" href="https://dist.apache.org/repos/dist/dev/maven/maven-3">https://dist.apache.org/repos/dist/dev/maven/maven-3</a>/<code>$VERSION</code>. Then once the vote passed, svn move to <code>release</code> <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>/<code>$VERSION</code>.</p> -<p>The <code>release</code> tree directory to use as a model for <code>dev</code> staging is:</p> -<ul> +<p>The goal is to commit candidate release to svn <code>dev</code> tree <a class="externalLink" href="https://dist.apache.org/repos/dist/dev/maven/maven-3">https://dist.apache.org/repos/dist/dev/maven/maven-3</a>/<code>$VERSION</code>. Once the vote has passed, svn move to <code>release</code> <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>/<code>$VERSION</code>.</p> +<p>The tree directory is:</p> + +<div class="source"> +<div class="source"><pre class="prettyprint linenums">https://dist.apache.org/repos/dist/dev/maven/maven-3/ + `-- $VERSION/ + |-- binaries/ + | |-- apache-maven-$VERSION-bin.tar.gz + | |-- apache-maven-$VERSION-bin.tar.gz.asc + | |-- apache-maven-$VERSION-bin.tar.gz.sha512 + | |-- apache-maven-$VERSION-bin.zip + | |-- apache-maven-$VERSION-bin.zip.asc + | `-- apache-maven-$VERSION-bin.zip.sha512 + `-- source/ (notice: singular...) + |-- apache-maven-$VERSION-src.tar.gz + |-- apache-maven-$VERSION-src.tar.gz.asc + |-- apache-maven-$VERSION-src.tar.gz.sha512 + |-- apache-maven-$VERSION-src.zip + |-- apache-maven-$VERSION-src.zip.asc + `-- apache-maven-$VERSION-src.zip.sha512 +</pre></div></div> -<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><code>$VERSION</code>/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><code>$VERSION</code>/source (notice: singular…)</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> <p>For non-alpha/beta releases, release candidates are produced before the actual release.</p> Modified: maven/website/content/maven-site-1.0-site.jar ============================================================================== Binary files - no diff available.