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 5b6b9b5 explicit inline tree, based on dist/dev snv url
5b6b9b5 is described below
commit 5b6b9b5771ca8acecbfc98d415cbbd3ad5b69586
Author: Hervé Boutemy <hbout...@apache.org>
AuthorDate: Sat Mar 27 17:07:59 2021 +0100
explicit inline tree, based on dist/dev snv url
---
.../developers/release/maven-core-release.md | 24 ++++++++++++++++++----
1 file changed, 20 insertions(+), 4 deletions(-)
diff --git a/content/markdown/developers/release/maven-core-release.md
b/content/markdown/developers/release/maven-core-release.md
index 73eff86..b663007 100644
--- a/content/markdown/developers/release/maven-core-release.md
+++ b/content/markdown/developers/release/maven-core-release.md
@@ -19,12 +19,28 @@ under the License.
-->
Maven differs slightly in its release process due to several extra steps.
-The goal is to commit candidate release to svn `dev` tree
<https://dist.apache.org/repos/dist/dev/maven/maven-3>/`$VERSION`. Then once
the vote passed, svn move to `release`
<https://dist.apache.org/repos/dist/release/maven/maven-3>/`$VERSION`.
+The goal is to commit candidate release to svn `dev` tree
<https://dist.apache.org/repos/dist/dev/maven/maven-3>/`$VERSION`. Once the
vote has passed, svn move to `release`
<https://dist.apache.org/repos/dist/release/maven/maven-3>/`$VERSION`.
-The `release` tree directory to use as a model for `dev` staging is:
+The tree directory is:
-- https://dist.apache.org/repos/dist/release/maven/maven-3/`$VERSION`/binaries
-- https://dist.apache.org/repos/dist/release/maven/maven-3/`$VERSION`/source
(notice: singular...)
+```
+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
+```
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
