This is an automated email from the ASF dual-hosted git repository.

snoopdave pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/roller-website.git


The following commit(s) were added to refs/heads/asf-site by this push:
     new 9e2b303  5.2.2 release, plus a note about SHA256
9e2b303 is described below

commit 9e2b303283d006c09c5ffc16c992614fad71a4c6
Author: Dave Johnson <[email protected]>
AuthorDate: Thu Jan 10 18:29:31 2019 -0500

    5.2.2 release, plus a note about SHA256
---
 sources/src/main/jbake/content/downloads/downloads.md | 8 +++-----
 1 file changed, 3 insertions(+), 5 deletions(-)

diff --git a/sources/src/main/jbake/content/downloads/downloads.md 
b/sources/src/main/jbake/content/downloads/downloads.md
index 067601a..74b72a2 100644
--- a/sources/src/main/jbake/content/downloads/downloads.md
+++ b/sources/src/main/jbake/content/downloads/downloads.md
@@ -8,14 +8,13 @@ type=page
 Releases of the Apache Roller blog server are made available to the general 
public at no charge, under the <a href="http://apache.org/licenses/";>Apache 
License,</a> in both binary and source distributions.
 
 ### General Availability (GA) Releases</strong> - <em>Ready for Prime 
Time!</em>
-__<a 
href="http://www.apache.org/dyn/closer.cgi/roller/roller-5.2/v5.2.1/";>Roller 
5.2.1</a> (&quot;best available&quot;)__
+__<a 
href="http://www.apache.org/dyn/closer.cgi/roller/roller-5.2/v5.2.2/";>Roller 
5.2.2</a> (&quot;best available&quot;)__
 
 Previous source and binary distributions, including documentation, are 
available in the <a class="external" 
href="http://archive.apache.org/dist/roller/";>Apache archives</a>.
 
 Project releases are approved by vote of the Apache Roller Project Management 
Committee (PMC). Support for a release is provided by project volunteers on the 
project <a 
href="https://cwiki.apache.org/confluence/display/ROLLER/How+to+ask+for+help";>mailing
 lists</a>. Bugs found in a release may be discussed on the list and reported 
through the <a href="https://issues.apache.org/jira/browse/ROL";>issue 
tracker</a>. The user mailing list and issue tracker are the 
<strong>only</strong> support [...]
 
-
-Note: When downloading from a mirror, please be sure to verify that checksums 
and signatures are correct. To do so, use the checksum and signature files from 
the main Apache site at <a class="external" 
href="http://www.apache.org/dyn/closer.cgi/roller/roller-5.2/v5.2.1/bin/";>http://www.apache.org/dyn/closer.cgi/roller/roller-5.2/v5.2.1/bin/</a>
+Note: When downloading from a mirror, please be sure to verify that checksums 
and signatures are correct. To do so, use the checksum and signature files from 
the main Apache site at <a class="external" 
href="http://www.apache.org/dyn/closer.cgi/roller/roller-5.2/v5.2.2/bin/";>http://www.apache.org/dyn/closer.cgi/roller/roller-5.2/v5.2.2/bin/</a>
 Find here the KEYS file, which contains all OpenPGP keys we use to sign 
releases:
 <a class="external" 
href="http://www.apache.org/dist/roller/";>http://www.apache.org/dist/roller/</a>
 
@@ -34,8 +33,7 @@ or
     % gpg --import KEYS
     % gpg --verify ${filename}.tar.gz.asc
 
-Alternatively, you can verify the MD5 signature on the files. A Unix program 
called
-``md5`` or ``md5sum`` is included in many Unix distributions. It is also 
available as part of <a 
href="http://www.gnu.org/software/textutils/textutils.html";>GNU Textutils.</a> 
Windows users can get binary md5 programs from <a 
href="http://www.fourmilab.ch/md5/";>here,</a> <a 
href="http://www.pc-tools.net/win32/freeware/console/";>here,</a> or <a 
href="http://www.slavasoft.com/fsum/";>here</a>.
+Alternatively you can also verify the SHA256 checksum for each file. Apache 
Open Office provides a nice guide to verifying checksum here <a 
href="https://www.openoffice.org/download/checksums.html";>How to verify the 
integrity of the downloaded file?</a>.
 
 If you want to build directly from the sources, please check the <a 
href="https://cwiki.apache.org/confluence/display/ROLLER/How+to+build+Roller";>Project
 Wiki</a>.
 

Reply via email to