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

clr pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/db-jdo-site.git


The following commit(s) were added to refs/heads/master by this push:
     new 33576aa  Update release-3.1.adoc
33576aa is described below

commit 33576aace327cfe1a0b3459ebd305a95a0d6d864
Author: Craig L Russell <apache....@gmail.com>
AuthorDate: Mon Feb 17 10:37:08 2020 -0800

    Update release-3.1.adoc
    
    Add reference to git repository. Remove references to full 8MB download.
    Improve formatting of verification instructions
---
 src/main/asciidoc/release-3.1.adoc | 52 +++++++++++++++++++++++---------------
 1 file changed, 32 insertions(+), 20 deletions(-)

diff --git a/src/main/asciidoc/release-3.1.adoc 
b/src/main/asciidoc/release-3.1.adoc
index bd86326..7fbd565 100644
--- a/src/main/asciidoc/release-3.1.adoc
+++ b/src/main/asciidoc/release-3.1.adoc
@@ -10,30 +10,36 @@ image:images/jdo_text.png[float="left"]
 :titlepage:
 :grid: cols
 
-== JDO 3.1 Distributionsanchor:JDO_3.1_Distributions[]
+= JDO 3.1 Distributionsanchor:JDO_3.1_Distributions[]
 
-Use the links below to download Apache JDO from one of our mirrors.
+If you intend to develop JDO (make modifications to the JDO code), you should
+clone the public repository and submit pull requests if desired.
+You can use this url: https://github.com/apache/db-jdo.git[db-jdo.git]
 
-It is essential to xref:Verifying[verify the integrity] of the
-distribution files.
+To develop your own code to use JDO, you can use the links below
+to download Apache JDO from one of the official ASF mirrors.
+If you are using Maven, you can declare a dependency using the instructions 
below.
 
+It is essential to xref:Verifying[verify the integrity] of the
+distribution files after downloading any artifacts.
 
-=== Release Notesanchor:Release_Notes[]
+== Release Notesanchor:Release_Notes[]
 
 
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12325878&styleName=Html&projectId=10630[View
 release notes for JDO 3.1]
 
-=== APIanchor:API[]
+== APIanchor:API[]
 
 The api project contains source to build jdo-api.jar, which defines the
 JDO API. The jar file is the only artifact needed for users who wish to
 compile their programs using the JDO API.
 
-https://www.apache.org/dyn/closer.lua/db/jdo/3.1/jdo-api-3.1.jar[3.1 api.jar]
-https://www.apache.org/dist/db/jdo/3.1/jdo-api-3.1.jar.asc[asc]
-https://www.apache.org/dist/db/jdo/3.1/jdo-api-3.1.jar.sha1[sha1]
+https://www.apache.org/dyn/closer.lua/db/jdo/3.1/jdo-api-3.1-sources.jar[jdo 
3.1 api-sources.jar]
+https://www.apache.org/dist/db/jdo/3.1/jdo-api-3.1-sources.jar.asc[asc]
+https://www.apache.org/dist/db/jdo/3.1/jdo-api-3.1-sources.jar.sha1[sha1]
+https://www.apache.org/dist/db/jdo/3.1/jdo-api-3.1-sources.jar.md5[md5]
 
-== Maven (convenience binary)anchor:Maven[]
+=== Maven (convenience binary)anchor:Maven[]
 
 The JDO API can be downloaded
 automatically by maven and placed into the local maven repository if you
@@ -46,7 +52,7 @@ For example:
   <version>3.1</version>
 </dependency>
 
-=== TCKanchor:TCK[]
+== TCKanchor:TCK[]
 
 This is a download for all implementors of JDO, and for those who want
 to check how well an implementation is compliant with the JDO
@@ -59,19 +65,17 @@ the JDO project including the API, TCK, and test artifacts.
 The dependencies are automatically downloaded by
 maven as needed to run the TCK. 
 
-Please refer to the README.html for further details.
-
-https://www.apache.org/dyn/closer.lua/db/jdo/3.1/jdo-3.1-source-release.zip[3.1
 source-release.zip (8 MB)]
-https://www.apache.org/dist/db/jdo/3.1/jdo-3.1-source-release.zip.asc[asc]
-https://www.apache.org/dist/db/jdo/3.1/jdo-3.1-source-release.zip.sha1[sha1]
+Please refer to the README for further details.
 
 https://www.apache.org/dyn/closer.lua/db/jdo/3.1/jdo-3.1-src.tar.gz[3.1 
src.tar.gz (1.1 MB)]
 https://www.apache.org/dist/db/jdo/3.1/jdo-3.1-src.tar.gz.asc[asc]
 https://www.apache.org/dist/db/jdo/3.1/jdo-3.1-src.tar.gz.sha1[sha1]
+https://www.apache.org/dist/db/jdo/3.1/jdo-3.1-src.tar.gz.md5[md5]
 
 https://www.apache.org/dyn/closer.lua/db/jdo/3.1/jdo-3.1-src.zip[3.1 src.zip 
(2.8 MB)]
 https://www.apache.org/dist/db/jdo/3.1/jdo-3.1-src.zip.asc[asc]
 https://www.apache.org/dist/db/jdo/3.1/jdo-3.1-src.zip.sha1[sha1]
+https://www.apache.org/dist/db/jdo/3.1/jdo-3.1-src.zip.md5[md5]
 
 == Verifying Releasesanchor:Verifying_Releases[]
 
@@ -85,10 +89,18 @@ https://www.apache.org/dist/db/jdo/KEYS[KEYS] as well as 
the `asc`
 signature file for the particular distribution. Make sure you get these
 files from the https://www.apache.org/dist/db/jdo/[main distribution
 directory], rather than from a mirror. Then verify the signatures using
+these commands (depending on your tool set):
 
-` % pgpk -a KEYS % pgpv release_name.tar.gz.asc` _or_ +
-` % pgp -ka KEYS % pgp release_name.tar.gz.asc` _or_ +
-` % gpg --import KEYS % gpg --verify release_name.tar.gz.asc`
+[source]
+% pgpk -a KEYS 
+% pgpv release_name.tar.gz.asc
+
+[source]
+% pgp -ka KEYS
+% pgp release_name.tar.gz.asc
+
+[source]
+% gpg --import KEYS
+% gpg --verify release_name.tar.gz.asc
 
-'''''
 

Reply via email to