sis-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r904608 - in /websites/staging/sis/trunk/content: ./ downloads.html index.html release-management.html
Date Wed, 02 Apr 2014 04:07:24 GMT
Author: buildbot
Date: Wed Apr  2 04:07:23 2014
New Revision: 904608

Staging update by buildbot for sis

    websites/staging/sis/trunk/content/   (props changed)

Propchange: websites/staging/sis/trunk/content/
--- cms:source-revision (original)
+++ cms:source-revision Wed Apr  2 04:07:23 2014
@@ -1 +1 @@

Modified: websites/staging/sis/trunk/content/downloads.html
--- websites/staging/sis/trunk/content/downloads.html (original)
+++ websites/staging/sis/trunk/content/downloads.html Wed Apr  2 04:07:23 2014
@@ -101,12 +101,12 @@ See the <code>NOTICE</code> file contain
 <h1 id="bundles">Download ZIP files</h1>
-<p>Apache SIS 0.3 is now available.
+<p>Apache SIS 0.4 is now available.
 See the <code>CHANGES</code> file for more information on the list of updates
in this initial release.</p>
-<li><a href="">Apache
SIS-0.3 sources</a> [<a href="">PGP</a>]</li>
-<li><a href="">Apache
SIS-0.3 javadoc</a> [<a href="">PGP</a>]</li>
-<li><a href="">Apache
SIS 0.3 binary</a> [<a href="">PGP</a>]</li>
+<li><a href="">Apache
SIS-0.4 sources</a> [<a href="">PGP</a>]</li>
+<li><a href="">Apache
SIS-0.4 javadoc</a> [<a href="">PGP</a>]</li>
+<li><a href="">Apache
SIS 0.4 binary</a> [<a href="">PGP</a>]</li>
 <p>The PGP (<em>Pretty Good Privacy</em>) signatures can be verified using
any OpenPGP implementation, for example GPG (<em>GNU Privacy Guard</em>).
 First download the <code>[KEYS][keys]</code> file as well as the <code>.asc</code>
signature files for the relevant release packages.
@@ -131,14 +131,14 @@ pgpv
 <h2 id="release-notes">Release notes</h2>
-<p>See the <a href="release-notes/0.3.html">release notes</a> for a list
of changes since the previous version.</p>
+<p>See the <a href="release-notes/0.4.html">release notes</a> for a list
of changes since the previous version.</p>
 <h1 id="maven">Download as a Maven dependency</h1>
 <p>An easy approach to integrate SIS into a Java project uses the <a href="">Apache
 dependency management tool to automatically obtain the required Java Archives (JAR) files
from the network.
 Below are examples of declarations in a <code>pom.xml</code> file for building
a project with the SIS core module:</p>
 <h2 id="maven-release">Using SIS releases</h2>
 <div class="codehilite"><pre><span class="nt">&lt;properties&gt;</span>
-  <span class="nt">&lt;sis.version&gt;</span>0.3<span class="nt">&lt;/sis.version&gt;</span>
+  <span class="nt">&lt;sis.version&gt;</span>0.4<span class="nt">&lt;/sis.version&gt;</span>
 <span class="nt">&lt;/properties&gt;</span>
 <span class="nt">&lt;dependencies&gt;</span>

Modified: websites/staging/sis/trunk/content/index.html
--- websites/staging/sis/trunk/content/index.html (original)
+++ websites/staging/sis/trunk/content/index.html Wed Apr  2 04:07:23 2014
@@ -97,8 +97,8 @@ The SIS storage modules will provide a c
 simple imagery as to many dimensional data structures.</p>
 <h2 id="user">Using SIS</h2>
 <p>SIS requires a Java 6 Runtime Environment.
-The latest release is 0.3, released August 2013.
-The version under development is 0.4-SNAPSHOT.</p>
+The latest release is 0.4, released April 2014.
+The version under development is 0.5-SNAPSHOT.</p>
 <li><a href="downloads.html">Downloads</a> as a <code>zip</code>
files, or as Maven dependencies.</li>
 <li><a href="command-line.html">Command-line interface</a> for an overview
of a command-line tool.</li>

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 Wed Apr  2 04:07:23 2014
@@ -137,8 +137,8 @@ The intended audiences are SIS release m
 <p>For all instructions in this page, <code>$OLD_VERSION</code> and <code>$NEW_VERSION</code>
stand for the version
 number of the previous and the new release respectively, and <code>$RELEASE_CANDIDATE</code>
stands for
 the current release attempt. Those versions shall be set on the command line like below (Unix):</p>
-<div class="codehilite"><pre><span class="nb">export </span><span
class="nv">OLD_VERSION</span><span class="o">=</span>0.3
-<span class="nb">export </span><span class="nv">NEW_VERSION</span><span
+<div class="codehilite"><pre><span class="nb">export </span><span
class="nv">OLD_VERSION</span><span class="o">=</span>0.4
+<span class="nb">export </span><span class="nv">NEW_VERSION</span><span
 <span class="nb">export </span><span class="nv">RELEASE_CANDIDATE</span><span
 <span class="nb">export </span><span class="nv">SIGNING_KEY</span><span
class="o">=</span>&lt;your key ID&gt;
@@ -222,12 +222,12 @@ but also in a few Java files. The follow
 <p>Open the root <code>pom.xml</code> file in an editor and perform the
following changes:</p>
-<li>Copy-and-paste the whole <code>&lt;plugin&gt;</code> section
for <code>maven-javadoc-plugin</code> from <code>&lt;reporting&gt;</code>
to <code>&lt;build&gt;</code>.
+<li>Copy-and-paste the whole <code>&lt;plugin&gt;</code> block,
except <code>&lt;reportSets&gt;</code>, for <code>maven-javadoc-plugin</code>
from <code>&lt;reporting&gt;</code> to <code>&lt;build&gt;</code>.
     We need the javadoc configuration to be duplicated in both <code>&lt;reporting&gt;</code>
and <code>&lt;build&gt;</code> sections in order
     to get the expected Javadoc output in both Maven site and in the <code>*-javadoc.jar</code>
files to deployed in the
     Maven repository. <strong>TODO:</strong> see if upgrading Maven or the <code>maven-javadoc-plugin</code>
can solve this problem.</li>
-<li>Remove the whole <code>&lt;pluginRepositories&gt;</code> section,
since it should not be needed for releases (and is actually not allowed).</li>
-<li>Remove the <code>&lt;plugin&gt;</code> section for <code>docbkx-maven-plugin</code>,
since the DocBook directory is omitted (see below).</li>
+<li>Remove the whole <code>&lt;pluginRepositories&gt;</code> block,
since it should not be needed for releases (and is actually not allowed).</li>
+<li>Remove the <code>&lt;plugin&gt;</code> block for <code>docbkx-maven-plugin</code>,
since the DocBook directory is omitted (see below).</li>
 <p>Recursively delete the <code>src/main/docbook</code> directory (this
policy may be revised in future SIS releases).
 We omit this directory for now because this material may move to the CMS, and no English
version is available yet.</p>
@@ -417,7 +417,8 @@ mv <span class="nv">$TAG_DIR</span>/targ
 <p>Rename the files to something more conform to the convention seen in other Apache
-<div class="codehilite"><pre>mv sis-<span class="nv">$NEW_VERSION</span>
    apache-sis-<span class="nv">$NEW_VERSION</span>
+<div class="codehilite"><pre>mv apache-sis-<span class="nv">$NEW_VERSION</span>.zip
            apache-sis-<span class="nv">$NEW_VERSION</span>
+mv sis-<span class="nv">$NEW_VERSION</span>     apache-sis-<span
 mv sis-<span class="nv">$NEW_VERSION</span> apache-sis-<span
@@ -577,7 +578,8 @@ svn delete
-<p>Report the changes manually on the JDK6 and JDK7 branches.</p>
+<p>Edit the version number in the <code>application/sis-console/src/main/artifact/README</code>
+Report the changes manually on the JDK6 and JDK7 branches.</p>

View raw message