sis-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r1050718 - in /websites/staging/sis/trunk/content: ./ DOAP.rdf command-line.html release-management-setup.html release-management.html
Date Fri, 27 Sep 2019 14:31:03 GMT
Author: buildbot
Date: Fri Sep 27 14:31:03 2019
New Revision: 1050718

Log:
Staging update by buildbot for sis

Modified:
    websites/staging/sis/trunk/content/   (props changed)
    websites/staging/sis/trunk/content/DOAP.rdf
    websites/staging/sis/trunk/content/command-line.html
    websites/staging/sis/trunk/content/release-management-setup.html
    websites/staging/sis/trunk/content/release-management.html

Propchange: websites/staging/sis/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Sep 27 14:31:03 2019
@@ -1 +1 @@
-1867211
+1867637

Modified: websites/staging/sis/trunk/content/DOAP.rdf
==============================================================================
Binary files - no diff available.

Modified: websites/staging/sis/trunk/content/command-line.html
==============================================================================
--- websites/staging/sis/trunk/content/command-line.html (original)
+++ websites/staging/sis/trunk/content/command-line.html Fri Sep 27 14:31:03 2019
@@ -112,7 +112,7 @@ in their own application.</p>
 </li>
 <li><a href="#usage">Usage</a></li>
 <li><a href="#examples">Examples</a><ul>
-<li><a href="#crs">Getting ISO 19111 Coordinate Reference Systems (CRS)</a></li>
+<li><a href="#crs">Print Coordinate Reference Systems (CRS) definition</a></li>
 <li><a href="#identifier">Getting a verified EPSG identifier from a Coordinate
Reference System</a></li>
 <li><a href="#coordinateOperation">Performing coordinate conversions or transformations</a></li>
 <li><a href="#metadata">Extracting ISO 19115 Metadata</a></li>
@@ -144,13 +144,21 @@ Example:</p>
 If not, the same examples can still be executed by replacing the <code>sis</code>
command by <code>./apache-sis-1.0/bin/sis</code>.</p>
 <h2 id="dependencies">Optional dependencies<a class="headerlink" href="#dependencies"
title="Permanent link">&para;</a></h2>
 <p>Every JAR files present in the <code>lib</code> sub-directory will be
included on the classpath during <code>sis</code> command execution.
-By default, the <code>lib</code> directory contains the <code>sis.jar</code>
file with only Derby and JAXB dependencies.
+By default, the <code>lib</code> directory contains the <code>sis.jar</code>
file with only GeoAPI JAXB API dependencies.
 However users can add other JAR files in that directory for the following optional dependencies:</p>
 <ul>
-<li><strong>UCAR netCDF library —</strong>
+<li>
+<p><strong>Derby driver —</strong>
+    needed only if Apache SIS can not locate a JavaDB driver in the JDK installation directory.
+    This is not needed on Oracle JDK8 distribution, but needed for all OpenJDK versions and
for
+    Oracle JDK more recent than 8.</p>
+</li>
+<li>
+<p><strong>UCAR netCDF library —</strong>
     by default, SIS uses its own embedded netCDF reader which supports only the classical
netCDF format, as standardized by OGC.
     If there is a need to read files encoded in GRID or HDF formats, then one can copy the
UCAR netCDF library in the <code>lib</code> sub-directory.
-    If presents, the UCAR library should be detected and used automatically when SIS can
not read a netCDF file by itself.</li>
+    If presents, the UCAR library should be detected and used automatically when SIS can
not read a netCDF file by itself.</p>
+</li>
 </ul>
 <h1 id="usage">Usage<a class="headerlink" href="#usage" title="Permanent link">&para;</a></h1>
 <p>Invoking <code>sis</code> without argument shows a summary of available
commands and all options.
@@ -198,7 +206,7 @@ When two such CRS are known (the <em>sou
 However the coordinate operation depends not only on the source and target CRS, but also
on the <em>area of interest</em> as shown
 by the example transforming city coordinates in USA and in Canada.
 Then another example show how to get a wider set of metadata, with the CRS as only one specific
element of those metadata.</p>
-<h2 id="crs">Getting ISO 19111 Coordinate Reference Systems (CRS)<a class="headerlink"
href="#crs" title="Permanent link">&para;</a></h2>
+<h2 id="crs">Print Coordinate Reference Systems (CRS) definition<a class="headerlink"
href="#crs" title="Permanent link">&para;</a></h2>
 <p>Apache SIS can read Coordinate Reference System (CRS) definitions from various sources:</p>
 <ul>
 <li>Codes from the EPSG geodetic dataset</li>
@@ -213,12 +221,8 @@ For example the following command prints
 </pre></div>
 
 
-<p>The first time that a command requires the EPSG dataset, Apache SIS will propose
to download and install a local copy.
-This automatic download happen only when using the command-line tools described in this page.
-Developers who wish to use the EPSG dataset in their applications can use the Maven artifact
-documented in <a href="downloads.html#epsg">download</a> page.</p>
 <p><details>
-  <summary>The above command should produce the following output (click to expand):</summary>
+  <summary>Expected output (click to expand):</summary>
 <pre>ProjectedCRS["JGD2011 / Japan Plane Rectangular CS VIII",
   BaseGeodCRS["JGD2011",
     Datum["Japanese Geodetic Datum 2011",
@@ -241,16 +245,31 @@ documented in <a href="downloads.html#ep
   Id["EPSG", 6676, "9.7", URI["urn:ogc:def:crs:EPSG:9.7:6676"]],
   Remark["Replaces JGD2000 / Japan Plane Rectangular CS VIII (CRS code 2450) with effect
from 21st October 2011."]]</pre>
 </details></p>
+<p>The first time that a command requires the EPSG dataset, Apache SIS will propose
to download and install a local copy.
+This automatic download happen only when using the command-line tools described in this page.
+Developers who wish to use the EPSG dataset in their applications can use the Maven artifact
+documented in <a href="downloads.html#epsg">download</a> page.
+If Apache SIS does not propose to download the EPSG geodetic dataset, it may be because no
Derby database has been found.
+Try to add the Derby optional dependency <a href="./epsg.html#command-line">as documented
here</a>.</p>
 <p>The above output is compatible with version 2 of <em>Well Known Text</em>
(WKT) format.
-However some applications are restricted to WKT version 1.
-For an output using the legacy WKT 1 format, one can add the <code>--format wkt1</code>
option to the above command-line.</p>
+The output format can be controlled as below:</p>
+<ul>
+<li>
+<p>Some applications are restricted to WKT version 1.
+    For an output using the legacy WKT 1 format, one can add the <code>--format wkt1</code>
option to the above command-line.</p>
+</li>
+<li>
 <p>The “WKT 2” specification allows some flexibility in keyword names and
in the way to specify units of measurement.
-By default, the command-line uses this flexibility for producing less verbose but still legal
WKT 2 output.
-If an output closer to WKT 2 recommendations is desired, one can add the <code>--format
wkt2</code> option to the above command.
-The result will be slightly more verbose.</p>
+    By default, the command-line uses this flexibility for producing less verbose but still
legal WKT 2 output.
+    If an output closer to WKT 2 recommendations is desired, one can add the <code>--format
wkt2</code> option to the above command.
+    The result will be slightly more verbose.</p>
+</li>
+<li>
 <p>Apache SIS can also read and write CRS definitions in the <em>Geographic Markup
Language</em> (GML) format.
-For GML output, one can add the <code>--format xml</code> option to the above
command.
-The result will be much more verbose than WKT outputs.</p>
+    For GML output, one can add the <code>--format xml</code> option to the above
command.
+    The result will be much more verbose than WKT outputs.</p>
+</li>
+</ul>
 <p>Java API for accessing functionalities shown in above examples are:</p>
 <ul>
 <li>Convenience static methods in <code>org.apache.sis.referencing</code>
package:<ul>
@@ -278,8 +297,8 @@ Such codes can be written in different w
 <p>In a <em>Well Known Text</em> (WKT) string, the code can appear at the
bottom of the definition
 in an optional element like <code>ID["EPSG", 4326]</code> or <code>AUTHORITY["EPSG",
"4326"]</code>.
 However in many cases the code is missing.
-Sometime Apache SIS can find a missing code by comparing a given CRS against the definitions
in the EPSG database.</p>
-<p>The following example reads a WKT for the <em>“NTF (Paris) / Lambert
zone II”</em> Coordinate Reference System,
+Sometime Apache SIS can find a missing code by comparing a given CRS against the definitions
in the EPSG database.
+The following example reads a WKT for the <em>“NTF (Paris) / Lambert zone II”</em>
Coordinate Reference System,
 but in which the <code>ID["EPSG", 27572]</code> element has been intentionally
omitted.
 Furthermore, the <em>“NTF (Paris) / Lambert zone II”</em> name has
been replaced by <em>“NTF (Paris) / zone to be discovered by the demo”</em>
name.
 Executing the following command:</p>

Modified: websites/staging/sis/trunk/content/release-management-setup.html
==============================================================================
--- websites/staging/sis/trunk/content/release-management-setup.html (original)
+++ websites/staging/sis/trunk/content/release-management-setup.html Fri Sep 27 14:31:03 2019
@@ -120,19 +120,21 @@ However in the later case, all relative
 ├─ non-free
 │  ├─ sis-epsg
 │  └─ sis-embedded-data
-├─ distribution
-├─ release-test
-│  └─ maven
+├─ releases
+│  ├─ distribution
+│  └─ integration-test
+│     └─ maven
 └─ site
 </pre></div>
 
 
 <p>Create the above directory structure as below:</p>
-<div class="codehilite"><pre>git clone    https://gitbox.apache.org/repos/asf/sis.git
master
+<div class="codehilite"><pre>mkdir releases
+git clone    https://gitbox.apache.org/repos/asf/sis.git master
 svn checkout https://svn.apache.org/repos/asf/sis/data/non-free
-svn checkout https://svn.apache.org/repos/asf/sis/release-test
 svn checkout https://svn.apache.org/repos/asf/sis/site/trunk site
-svn checkout https://dist.apache.org/repos/dist/dev/sis distribution
+svn checkout https://svn.apache.org/repos/asf/sis/release-test releases/integration-test
+svn checkout https://dist.apache.org/repos/dist/dev/sis releases/distribution
 </pre></div>
 
 

Modified: websites/staging/sis/trunk/content/release-management.html
==============================================================================
--- websites/staging/sis/trunk/content/release-management.html (original)
+++ websites/staging/sis/trunk/content/release-management.html Fri Sep 27 14:31:03 2019
@@ -172,12 +172,16 @@ the current release attempt. Those versi
 a result of the steps). Any other layout can be used. However if the layout differs, then
the relative paths
 in this page shall be adjusted accordingly.</p>
 <div class="codehilite"><pre>&lt;any root directory for SIS&gt;
+├─ $NEW_VERSION-RC
 ├─ master
 ├─ non-free
 │  └─ sis-epsg
-├─ distribution
-│  └─ $NEW_VERSION
-│     └─ RC$RELEASE_CANDIDATE
+├─ releases
+│  ├─ distribution
+│  │  └─ $NEW_VERSION
+│  │     └─ RC$RELEASE_CANDIDATE
+│  └─ integration-test
+│     └─ maven
 └─ site
    └─ content
       └─ apidocs
@@ -189,17 +193,19 @@ in this page shall be adjusted according
 <ul>
 <li><code>DOWNLOAD_URL</code> in <code>application/sis-console/src/main/java/org/apache/sis/console/ResourcesDownloader.java</code>
file.</li>
 <li><code>&lt;sis.non-free.version&gt;</code> in root <code>pom.xml</code>
file.</li>
-<li>Also review the <code>README</code> and <code>NOTICE</code>
files in root directory.</li>
+<li>Review the <code>README</code> and <code>NOTICE</code>
files in root directory.</li>
+<li>Review the <code>README</code> files in <code>application/sis-console/src/main/artifact/</code>
and subdirectories.</li>
 </ul>
 <p>If not already done, build the C/C++ code of <code>sis-gdal</code> module:</p>
-<div class="codehilite"><pre>storage/sis-gdal/src/main/c
+<div class="codehilite"><pre><span class="nb">cd </span>storage/sis-gdal/src/main/c
 make
 <span class="nb">cd</span> -
 </pre></div>
 
 
 <p>Commit and merge with other branches up to master.</p>
-<div class="codehilite"><pre>git commit --message<span class="o">=</span><span
class="s2">&quot;Set version number and the EPSG geodetic dataset URL to expected values
after release.&quot;</span>
+<div class="codehilite"><pre>git add --update
+git commit --message<span class="o">=</span><span class="s2">&quot;Set
version number and the EPSG geodetic dataset URL to expected values after release.&quot;</span>
 <span class="c"># merge with master</span>
 </pre></div>
 
@@ -260,7 +266,10 @@ Update <a href="http://issues.apache.org
     The <em>Sub Tasks</em> can be classified according the category of their
parent issue.</li>
 </ul>
 <p>Commit to staging area (not published immediately):</p>
-<div class="codehilite"><pre>svn add content/release-notes/<span class="nv">$NEW_VERSION</span>.html
+<div class="codehilite"><pre><span class="nb">cd</span> ../site
+cp content/release-notes/<span class="nv">$OLD_VERSION</span>.html content/release-notes/<span
class="nv">$NEW_VERSION</span>.html
+<span class="c"># Edit release notes before to continue.</span>
+svn add content/release-notes/<span class="nv">$NEW_VERSION</span>.html
 svn commit --message <span class="s2">&quot;Release notes for Apache SIS $NEW_VERSION.&quot;</span>
 </pre></div>
 
@@ -269,7 +278,8 @@ svn commit --message <span class="s2">&q
 <p>Execute the following commands.
 It is okay to checkout the branch in a separated directory if desired.
 The <code>SIS_RC_DIR</code> environment variable will specify that directory.</p>
-<div class="codehilite"><pre>git checkout -b <span class="nv">$NEW_VERSION</span>-RC
+<div class="codehilite"><pre><span class="nb">cd</span> ../master
+git checkout -b <span class="nv">$NEW_VERSION</span>-RC
 <span class="nb">cd</span> <span class="nv">$NEW_VERSION</span>-RC
 <span class="nb">export </span><span class="nv">SIS_RC_DIR</span><span
class="o">=</span><span class="sb">`</span><span class="nb">pwd</span><span
class="sb">`</span>
 </pre></div>
@@ -333,11 +343,7 @@ This profile performs the following acti
 </ul>
 <p>Each of those additional products may cause a failure that did not happen in normal
builds.</p>
 <div class="codehilite"><pre>mvn clean install --activate-profiles apache-release
-</pre></div>
-
-
-<p>Verify signature for all files:</p>
-<div class="codehilite"><pre>find . -name <span class="s2">&quot;sis-*.asc&quot;</span>
-exec gpg --verify <span class="s1">&#39;{}&#39;</span> <span class="se">\;</span>
+find . -name <span class="s2">&quot;sis-*.asc&quot;</span> -exec gpg
--verify <span class="s1">&#39;{}&#39;</span> <span class="se">\;</span>
    <span class="c"># Verify signatures.</span>
 </pre></div>
 
 
@@ -354,27 +360,17 @@ Replace occurrences of <code>&lt;version
 <div class="codehilite"><pre><span class="nb">cd</span> ../non-free
 svn update
 mvn clean install
+mvn javadoc:javadoc                   <span class="c"># Test that javadoc can be generated.</span>
 svn commit --message <span class="s2">&quot;Set version number and dependencies
to $NEW_VERSION.&quot;</span>
 </pre></div>
 
 
-<p>We deploy the non-free resources in a Nexus repository separated from the rest of
Apache SIS for allowing tests later.
-If there is any issue with this deployment, the staging repository can easily be dropped
and recreated.</p>
-<div class="codehilite"><pre>mvn deploy --activate-profiles apache-release
-</pre></div>
-
-
-<p>Note the URL printed by Maven to the console during the deployment phase.
-They will be needed for the next step.</p>
 <h2 id="integration-tests">Integration test<a class="headerlink" href="#integration-tests"
title="Permanent link">&para;</a></h2>
 <p>Open the root <code>pom.xml</code> file of integration tests.
 Set version numbers to <code>$NEW_VERSION</code> without <code>-SNAPSHOT</code>
suffix.
-Then go to the <code>&lt;url&gt;</code> declaration of the first <code>&lt;repository&gt;</code>
and replace value by the URL
-of the temporary Maven repository created by Nexus, as noted during deployment in above step.
-Usually, only the 3 last digits need to be updated.
 Verify the configuration and version of Maven plugins.
 Then test and commit (note that execution may be slow).</p>
-<div class="codehilite"><pre><span class="nb">cd</span> ../release-test
+<div class="codehilite"><pre><span class="nb">cd</span> ../distribution/integration-test
 svn update
 <span class="nb">cd </span>maven
 mvn clean <span class="nb">test</span>
@@ -388,16 +384,23 @@ svn commit --message <span class="s2">&q
 <ul>
 <li>Remove temporarily the <code>sis-openoffice</code> module from <code>application/pom.xml</code>.</li>
 <li>Remove the <code>test-jar</code> goal from <code>maven-jar-plugin</code>
in the root <code>pom.xml</code>.</li>
+<li>Remove all SIS dependencies declared with <code>&lt;type&gt;test-jar&lt;/type&gt;</code>
in all <code>pom.xml</code> files.
+    This hack will force us to skip test compilations.</li>
 </ul>
-<p>Then deploy SIS. Deploy also the non-free modules:</p>
-<div class="codehilite"><pre>mvn clean deploy --activate-profiles apache-release
+<p>Then deploy SIS (without test JAR files).
+Deploy also the non-free resources in a staging repository separated from the rest of Apache
SIS.
+If there is any issue with this deployment, the staging repository can easily be dropped
and recreated.</p>
+<div class="codehilite"><pre><span class="nb">cd</span> <span
class="nv">$SIS_RC_DIR</span>
+mvn clean deploy --activate-profiles apache-release --define maven.test.skip<span class="o">=</span><span
class="nb">true</span>
+<span class="nb">cd</span> ../non-free
+mvn clean deploy --activate-profiles apache-release
 </pre></div>
 
 
 <h2 id="nexus-close">Verify and close the Nexus release artifacts<a class="headerlink"
href="#nexus-close" title="Permanent link">&para;</a></h2>
 <p>Verify the staged artifacts in the <a href="https://repository.apache.org/index.html">Nexus
repository</a>.
 The artifacts can be found under <em>Build Promotion</em> → <em>Staging
repositories</em>, and searching for <code>org.apache.sis</code> in the
<em>Repository</em> column.
-Navigate through the artifact tree and make sure that all javadoc, source, test and jar files
have <code>.asc</code> (GPG signature) and <code>.md5</code> files.
+Navigate through the artifact tree and make sure that all javadoc, source and jar files have
<code>.asc</code> (GPG signature) and <code>.md5</code> files.
 Select any <code>*-javadoc.jar</code> file and click on the <cite>Archive
Browser</cite> tab on the right side.
 Select any <code>*.html</code> file which is known to use some of the custom
taglets defined in the <code>sis-build-helper</code> module.
 Click on that file and verify that the custom elements are rendered properly.
@@ -430,8 +433,8 @@ Open the root <code>pom.xml</code> file
 Then go to the <code>&lt;url&gt;</code> declaration of the first <code>&lt;repository&gt;</code>
and replace value by the URL
 of the temporary Maven repository created by Nexus.
 Usually, only the 3 last digits need to be updated.</p>
-<div class="codehilite"><pre><span class="nb">cd</span> ../../release-test/maven
-vim pom.xml
+<div class="codehilite"><pre><span class="nb">cd</span> ../releases/integration-test/maven
+<span class="c"># Edit &lt;url&gt; in pom.xml before to continue.</span>
 mvn compile
 svn commit -m <span class="s2">&quot;Test project for SIS $NEW_VERSION-RC$RELEASE_CANDIDATE&quot;</span>
 </pre></div>
@@ -451,7 +454,7 @@ mvn package --strict-checksums
 
 
 <p>Verify that the EPSG dataset has been created, then cleanup:</p>
-<div class="codehilite"><pre>ll <span class="nv">$SIS_DATA</span>
+<div class="codehilite"><pre>ll <span class="nv">$SIS_DATA</span>/Databases/SpatialMetadata
 mvn clean
 </pre></div>
 
@@ -459,6 +462,8 @@ mvn clean
 <h1 id="stage">Stage the source, binary and javadoc artifacts<a class="headerlink"
href="#stage" title="Permanent link">&para;</a></h1>
 <p>Generate the Javadoc:</p>
 <div class="codehilite"><pre><span class="nb">cd</span> <span
class="nv">$SIS_RC_DIR</span>
+git checkout .            <span class="c"># Discard local changes, in particular the
hack for excluding test files.</span>
+mvn clean install --activate-profiles apache-release
 mvn javadoc:aggregate
 <span class="nb">cd </span>target/site
 zip -9 -r apache-sis-<span class="nv">$NEW_VERSION</span>-doc.zip apidocs
@@ -469,7 +474,7 @@ zip -9 -r apache-sis-<span class="nv">$N
 <h2 id="dist">Initialize the distribution directory<a class="headerlink" href="#dist"
title="Permanent link">&para;</a></h2>
 <p>Create the directory for the new version and release candidate within the distribution
directory.
 The <code>$RELEASE_CANDIDATE</code> variable shall be the number of current release
attempt.</p>
-<div class="codehilite"><pre><span class="nb">cd</span> ../../distribution
+<div class="codehilite"><pre><span class="nb">cd</span> ../releases/distribution
 svn update
 mkdir -p <span class="nv">$NEW_VERSION</span>/RC<span class="nv">$RELEASE_CANDIDATE</span>
 svn add <span class="nv">$NEW_VERSION</span>
@@ -487,7 +492,7 @@ Update the file content if necessary.</p
 <p>Move the files generated by Maven to the distribution directory:</p>
 <div class="codehilite"><pre>mv <span class="nv">$SIS_RC_DIR</span>/target/sis-<span
class="nv">$NEW_VERSION</span>-* .
 mv <span class="nv">$SIS_RC_DIR</span>/target/site/apache-sis-<span class="nv">$NEW_VERSION</span>-*
.
-mv <span class="nv">$SIS_RC_DIR</span>/application/sis-console/target/distribution/apache-sis-<span
class="nv">$NEW_VERSION</span>.zip .
+mv <span class="nv">$SIS_RC_DIR</span>/target/distribution/apache-sis-<span
class="nv">$NEW_VERSION</span>.zip .
 </pre></div>
 
 
@@ -500,23 +505,23 @@ mv sis-<span class="nv">$NEW_VERSION</sp
 
 <h2 id="sign">Sign and commit<a class="headerlink" href="#sign" title="Permanent
link">&para;</a></h2>
 <p>Sign the source, javadoc and binary artifacts:</p>
-<div class="codehilite"><pre>shasum --algorithm 512 apache-sis-<span class="nv">$NEW_VERSION</span>-src.zip
&gt; apache-sis-<span class="nv">$NEW_VERSION</span>-src.zip.sha
-md5sum                 apache-sis-<span class="nv">$NEW_VERSION</span>-src.zip
&gt; apache-sis-<span class="nv">$NEW_VERSION</span>-src.zip.md5
+<div class="codehilite"><pre>shas512um apache-sis-<span class="nv">$NEW_VERSION</span>-src.zip
&gt; apache-sis-<span class="nv">$NEW_VERSION</span>-src.zip.sha
+md5sum    apache-sis-<span class="nv">$NEW_VERSION</span>-src.zip &gt; apache-sis-<span
class="nv">$NEW_VERSION</span>-src.zip.md5
 
-gpg --use-agent --armor --detach-sign --default-key <span class="nv">$SIGNING_KEY</span>
apache-sis-<span class="nv">$NEW_VERSION</span>-doc.zip
-shasum --algorithm 512 apache-sis-<span class="nv">$NEW_VERSION</span>-doc.zip
&gt; apache-sis-<span class="nv">$NEW_VERSION</span>-doc.zip.sha
-md5sum                 apache-sis-<span class="nv">$NEW_VERSION</span>-doc.zip
&gt; apache-sis-<span class="nv">$NEW_VERSION</span>-doc.zip.md5
-
-gpg --use-agent --armor --detach-sign --default-key <span class="nv">$SIGNING_KEY</span>
apache-sis-<span class="nv">$NEW_VERSION</span>-bin.zip
-shasum --algorithm 512 apache-sis-<span class="nv">$NEW_VERSION</span>-bin.zip
&gt; apache-sis-<span class="nv">$NEW_VERSION</span>-bin.zip.sha
-md5sum                 apache-sis-<span class="nv">$NEW_VERSION</span>-bin.zip
&gt; apache-sis-<span class="nv">$NEW_VERSION</span>-bin.zip.md5
+gpg --armor --detach-sign --default-key <span class="nv">$SIGNING_KEY</span>
apache-sis-<span class="nv">$NEW_VERSION</span>-doc.zip
+sha512sum apache-sis-<span class="nv">$NEW_VERSION</span>-doc.zip &gt; apache-sis-<span
class="nv">$NEW_VERSION</span>-doc.zip.sha
+md5sum    apache-sis-<span class="nv">$NEW_VERSION</span>-doc.zip &gt; apache-sis-<span
class="nv">$NEW_VERSION</span>-doc.zip.md5
+
+gpg --armor --detach-sign --default-key <span class="nv">$SIGNING_KEY</span>
apache-sis-<span class="nv">$NEW_VERSION</span>-bin.zip
+sha512sum apache-sis-<span class="nv">$NEW_VERSION</span>-bin.zip &gt; apache-sis-<span
class="nv">$NEW_VERSION</span>-bin.zip.sha
+md5sum    apache-sis-<span class="nv">$NEW_VERSION</span>-bin.zip &gt; apache-sis-<span
class="nv">$NEW_VERSION</span>-bin.zip.md5
 </pre></div>
 
 
 <p>Verify checksums and signatures:</p>
-<div class="codehilite"><pre>find . -name <span class="s2">&quot;*.md5&quot;</span>
-exec md5sum --check <span class="s1">&#39;{}&#39;</span> <span class="se">\;</span>
-find . -name <span class="s2">&quot;*.sha&quot;</span> -exec shasum --check
<span class="s1">&#39;{}&#39;</span> <span class="se">\;</span>
-find . -name <span class="s2">&quot;*.asc&quot;</span> -exec gpg --verify
<span class="s1">&#39;{}&#39;</span> <span class="se">\;</span>
+<div class="codehilite"><pre>find . -name <span class="s2">&quot;*.md5&quot;</span>
-exec md5sum    --check <span class="s1">&#39;{}&#39;</span> <span
class="se">\;</span>
+find . -name <span class="s2">&quot;*.sha&quot;</span> -exec sha512sum
--check <span class="s1">&#39;{}&#39;</span> <span class="se">\;</span>
+find . -name <span class="s2">&quot;*.asc&quot;</span> -exec gpg    
 --verify <span class="s1">&#39;{}&#39;</span> <span class="se">\;</span>
 </pre></div>
 
 
@@ -545,8 +550,8 @@ svn commit --message <span class="s2">&q
 
 <h2 id="test">Test the release<a class="headerlink" href="#test" title="Permanent
link">&para;</a></h2>
 <p>Execute the following commands in any temporary directory for testing the sources:</p>
-<div class="codehilite"><pre>wget --no-check-certificate https://dist.apache.org/repos/dist/dev/sis/<span
class="nv">$NEW_VERSION</span>/RC<span class="nv">$RELEASE_CANDIDATE</span>/apache-sis-<span
class="nv">$NEW_VERSION</span>-src.zip <span class="se">\</span>
-                            https://dist.apache.org/repos/dist/dev/sis/<span class="nv">$NEW_VERSION</span>/RC<span
class="nv">$RELEASE_CANDIDATE</span>/apache-sis-<span class="nv">$NEW_VERSION</span>-src.zip.asc
+<div class="codehilite"><pre>wget https://dist.apache.org/repos/dist/dev/sis/<span
class="nv">$NEW_VERSION</span>/RC<span class="nv">$RELEASE_CANDIDATE</span>/apache-sis-<span
class="nv">$NEW_VERSION</span>-src.zip <span class="se">\</span>
+     https://dist.apache.org/repos/dist/dev/sis/<span class="nv">$NEW_VERSION</span>/RC<span
class="nv">$RELEASE_CANDIDATE</span>/apache-sis-<span class="nv">$NEW_VERSION</span>-src.zip.asc
 <span class="c"># Test</span>
 gpg --verify apache-sis-<span class="nv">$NEW_VERSION</span>-src.zip.asc
 unzip apache-sis-<span class="nv">$NEW_VERSION</span>-src.zip
@@ -556,8 +561,8 @@ mvn install
 
 
 <p>Execute the following commands in any temporary directory for testing the binary:</p>
-<div class="codehilite"><pre>wget --no-check-certificate https://dist.apache.org/repos/dist/dev/sis/<span
class="nv">$NEW_VERSION</span>/RC<span class="nv">$RELEASE_CANDIDATE</span>/apache-sis-<span
class="nv">$NEW_VERSION</span>-bin.zip <span class="se">\</span>
-                            https://dist.apache.org/repos/dist/dev/sis/<span class="nv">$NEW_VERSION</span>/RC<span
class="nv">$RELEASE_CANDIDATE</span>/apache-sis-<span class="nv">$NEW_VERSION</span>-bin.zip.asc
+<div class="codehilite"><pre>wget https://dist.apache.org/repos/dist/dev/sis/<span
class="nv">$NEW_VERSION</span>/RC<span class="nv">$RELEASE_CANDIDATE</span>/apache-sis-<span
class="nv">$NEW_VERSION</span>-bin.zip <span class="se">\</span>
+     https://dist.apache.org/repos/dist/dev/sis/<span class="nv">$NEW_VERSION</span>/RC<span
class="nv">$RELEASE_CANDIDATE</span>/apache-sis-<span class="nv">$NEW_VERSION</span>-bin.zip.asc
 <span class="c"># Test</span>
 gpg --verify apache-sis-<span class="nv">$NEW_VERSION</span>-bin.zip.asc
 unzip apache-sis-<span class="nv">$NEW_VERSION</span>-bin.zip



Mime
View raw message