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 ca83121 site source is now in Git
ca83121 is described below
commit ca831215425a4c2d1d4df7d0ac647aac8c553580
Author: Hervé Boutemy <hbout...@apache.org>
AuthorDate: Tue Aug 27 19:49:51 2019 +0200
site source is now in Git
---
content/markdown/developers/release/maven-core-release.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/content/markdown/developers/release/maven-core-release.md
b/content/markdown/developers/release/maven-core-release.md
index 30eb606..71dcd48 100644
--- a/content/markdown/developers/release/maven-core-release.md
+++ b/content/markdown/developers/release/maven-core-release.md
@@ -20,7 +20,7 @@ For non-alpha/beta releases, release candidates are produced
before the actual r
Checkout https://dist.apache.org/repos/dist/dev/maven/maven-3 then create the
necessary directory tree.
-Copy the binaries and src-tar.gz with their md5/asc to the created directories.
+Copy the binaries and src-tar.gz with their sha512/asc to the created
directories.
To produce a release candidate, follow the first seven steps only from the
following procedure:
@@ -48,7 +48,7 @@ Edit
<https://github.com/apache/maven/blob/master/doap_Maven.rdf> to list the ne
#### Update the Release Notes and Web Site
-Checkout <https://svn.apache.org/repos/asf/maven/site/trunk>.
+Checkout Maven site source
<https://github.com/apache/maven-site/maven-site.git>.
Note that release notes can be created and checked in, but other changes
should not be checked in as it can be deployed 'live' at any time.
