sis-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r965124 - in /websites/staging/sis/trunk/content: ./ release-management.html release-notes/0.5.html release-notes/0.6.html
Date Fri, 11 Sep 2015 17:36:44 GMT
Author: buildbot
Date: Fri Sep 11 17:36:33 2015
New Revision: 965124

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 Fri Sep 11 17:36:33 2015
@@ -1 +1 @@

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 11 17:36:33 2015
@@ -82,7 +82,18 @@
           <section id="content" class="row">
             <article class="span12">
               <p class="page-title">Release management</p>
-              <p>This page describes how to create and deploy the SIS Maven artifacts,
binary bundle, javadoc and list of API changes.
+              <style type="text/css">
+/* The following code is added by
+   It was originally lifted from */
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
> .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink
{ visibility: visible }</style>
+<p>This page describes how to create and deploy the SIS Maven artifacts, binary bundle,
javadoc and list of API changes.
 The <a href="">Release FAQ</a> page describes
the foundation wide policies.
 The instructions on this page provide a summary suitable to SIS releases, together with SIS-specific
 The intended audiences are SIS release managers.</p>
@@ -130,7 +141,7 @@ The intended audiences are SIS release m
-<h1 id="requirements">Requirements</h1>
+<h1 id="requirements">Requirements<a class="headerlink" href="#requirements" title="Permanent
 <p>Before to perform a release, make sure that the following conditions hold:</p>
 <li>Commands will be executed in a Unix shell.</li>
@@ -154,7 +165,7 @@ The boot class path value is highly syst
 <li><code>/usr/lib/jvm/java-6/jre/lib/rt.jar</code> on some Linux distributions
(replace <code>java-6</code> by the actual directory name).</li>
on MacOS.</li>
-<h2 id="directory-layout">Directory layout</h2>
+<h2 id="directory-layout">Directory layout<a class="headerlink" href="#directory-layout"
title="Permanent link">&para;</a></h2>
 <p>The steps described in this page assume the following directory layout (some directories
will be created as
 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>
@@ -175,33 +186,33 @@ in this page shall be adjusted according
-<h2 id="java-update">Java updates</h2>
+<h2 id="java-update">Java updates<a class="headerlink" href="#java-update" title="Permanent
 <p>While we need a JDK6 installation for the <code>bootclasspath</code>
option, we do not recommend to use it for generating
 the binaries since JDK6 has reached its end of public updates (but not the end of commercial
 We recommend to create the release with JDK7 or JDK8 instead. Make sure that the JDK installation
 to be used for the release has been updated recently, since compilers may receive critical
bug fixes.
 For example the <code>javadoc</code> tool of older JDK versions was known to
generate HTML pages with a vulnerability in them.</p>
-<h1 id="prepare-source">Prepare site and source code</h1>
+<h1 id="prepare-source">Prepare site and source code<a class="headerlink" href="#prepare-source"
title="Permanent link">&para;</a></h1>
 <p>Before to start the release process:</p>
 <li>Review and update the <code>README</code> file on the <code>trunk</code>
source code repository.</li>
 <li>Review the <code>javac</code> and <code>javadoc</code>
warnings reported by Jenkins and fix at least the typos.</li>
 <li>Ensure that the <code>trunk</code> build is successful (including tests)
with JDK6, JDK7 and JDK8.</li>
-<h2 id="prepare-documentation">Documentation</h2>
+<h2 id="prepare-documentation">Documentation<a class="headerlink" href="#prepare-documentation"
title="Permanent link">&para;</a></h2>
 <p>Update <a href="">JIRA</a> tasks
and prepare release notes as below:</p>
 <li>Ensure that the <em>Fix Version</em> in issues resolved since the last
release includes this release version correctly.</li>
 <li>Ensure that all open issues are resolved or closed before proceeding further.</li>
 <li>On the <code>site</code> source code repository, create a <code>content/release-notes/$NEW_VERSION.html</code>
file with all the features added.</li>
 <li>Use <code>content/release-notes/$OLD_VERSION.html</code> as a template,
omitting everything between the <code>&lt;body&gt;</code> and <code>&lt;/body&gt;</code>
-<li>The release notes can be obtained from JIRA, by clicking on the <em>Versions</em>
tab → the version number → <em>Release notes</em>
+<li>The release notes can be obtained from JIRA, by clicking on the <em>Roadmap</em>
tab → the version number → <em>Release notes</em>
     and then configuring the release notes to display HTML format and copying it.
     A suggested approach would be to reorganize the release notes as
     <em>New Features</em>, then <em>Improvements</em>, then <em>Bug
Fixes</em>, then <em>Tests</em> and finally <em>Tasks</em>.
     The <em>Sub Tasks</em> can be classified according the category of their
parent issue.</li>
-<h2 id="prepare-website">Web site</h2>
+<h2 id="prepare-website">Web site<a class="headerlink" href="#prepare-website" title="Permanent
 <p>Review and update the <code>content/DOAP.rdf</code> file on the <code>site</code>
source code repository.
 Add a new <code>&lt;release&gt;</code> block for the new release with
the estimated release date.</p>
 <p>Update the version numbers from the old one to <code>$NEW_VERSION</code>
in the following files.</p>
@@ -218,7 +229,7 @@ svn commit --message <span class="s2">&q
 <p>The new web site will be published in the <a href="">staging
 It will not yet be published on <code></code>.</p>
-<h1 id="branch">Create branch and tag</h1>
+<h1 id="branch">Create branch and tag<a class="headerlink" href="#branch" title="Permanent
 <p>Execute the following command:</p>
 <div class="codehilite"><pre>svn copy
<span class="se">\</span>
<span class="nv">$NEW_VERSION</span>
<span class="se">\</span>
@@ -262,7 +273,7 @@ svn remove application/sis-javafx
-<h2 id="branch-verify">Verify content</h2>
+<h2 id="branch-verify">Verify content<a class="headerlink" href="#branch-verify"
title="Permanent link">&para;</a></h2>
 <p>Starts the GPG agent if not already done.
 This is for avoiding to be prompted many time for the passphrase in every modules to be built
by Maven.
 Note that MacOS users can skip this step if their passphrase is stored in the OS keychain,</p>
@@ -286,7 +297,7 @@ the changes that would have been committ
-<h2 id="tag">Tag the branch</h2>
+<h2 id="tag">Tag the branch<a class="headerlink" href="#tag" title="Permanent link">&para;</a></h2>
 <p>In theory, the next commands would be a real (non-dry) run of <code>mvn release:prepare</code>,
followed by <code>mvn release:perform</code>.
 However we perform those steps manually rather than relying on Maven for the following reasons:</p>
@@ -334,7 +345,7 @@ mvn clean release:clean
-<h1 id="maven-deploy">Deploy Maven artifacts</h1>
+<h1 id="maven-deploy">Deploy Maven artifacts<a class="headerlink" href="#maven-deploy"
title="Permanent link">&para;</a></h1>
 <p>Execute an <code>install</code> phase first (required for our custom
<code>sis-build-helper</code> plugin),
 and generate the binary artifact (<code>pack.gz</code> file). The later will
fail if duplicated
 class files or resources are found. Consequently building the <code>pack.gz</code>
file is an
@@ -354,7 +365,7 @@ svn revert . --recursive
-<h2 id="nexus-close">Verify and close the Nexus release artifacts</h2>
+<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="">Nexus
 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.</p>
@@ -383,7 +394,7 @@ so try to see at least one code snippet.
 <p>We will announce later (in the <cite>Put the release candidate up for a vote</cite>
section) on the <code>dev@</code> mailing list
 the availability of this temporary repository for testing purpose.</p>
-<h2 id="nexus-text">Test the Nexus release artifacts</h2>
+<h2 id="nexus-text">Test the Nexus release artifacts<a class="headerlink" href="#nexus-text"
title="Permanent link">&para;</a></h2>
 <p>Go to the test Maven project.
 Open the root <code>pom.xml</code> file and set the <code>&lt;version&gt;</code>
number to the SIS release to be tested.
 Then go to the <code>&lt;url&gt;</code> declaration of the first <code>&lt;repository&gt;</code>
and replace value by the URL
@@ -403,7 +414,7 @@ This will also verify the checksums.</p>
-<h1 id="stage">Stage the source, binary and javadoc artifacts</h1>
+<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. While not mandatory, we suggest to use JDK 8 or above for
getting the new look and feel,
 getting the Javadoc enhancements expected in future JDK releases (more dynamic pages),
 avoiding the security vulnerability discovered in the Javadoc tools of older JDK releases,
@@ -418,7 +429,7 @@ zip -9 -r apache-sis-<span class="nv">$N
-<h2 id="dist">Initialize the distribution directory</h2>
+<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
 The <code>$RELEASE_CANDIDATE</code> variable shall be the number of current release
 <div class="codehilite"><pre><span class="nb">cd</span> ../../distribution
@@ -449,7 +460,7 @@ mv sis-<span class="nv">$NEW_VERSION</sp
-<h2 id="sign">Sign and commit</h2>
+<h2 id="sign">Sign and commit<a class="headerlink" href="#sign" title="Permanent
 <p>Sign the source, javadoc and binary artifacts:</p>
 <div class="codehilite"><pre>gpg --print-md SHA512 apache-sis-<span class="nv">$NEW_VERSION</span>
&gt; apache-sis-<span class="nv">$NEW_VERSION</span>
 gpg --print-md MD5    apache-sis-<span class="nv">$NEW_VERSION</span>
&gt; apache-sis-<span class="nv">$NEW_VERSION</span>
@@ -478,7 +489,7 @@ svn commit --message <span class="s2">&q
-<h2 id="apidocs">Update online Javadoc</h2>
+<h2 id="apidocs">Update online Javadoc<a class="headerlink" href="#apidocs" title="Permanent
 <p>Copy the Javadoc to the web site staging directory:</p>
 <div class="codehilite"><pre><span class="nb">cd</span> ../site/content
 rm -r apidocs
@@ -494,7 +505,7 @@ svn commit --message <span class="s2">&q
-<h2 id="test">Test the release</h2>
+<h2 id="test">Test the release<a class="headerlink" href="#test" title="Permanent
 <p>Execute the following commands in any temporary directory for testing the sources:</p>
 <div class="codehilite"><pre>wget --no-check-certificate<span
class="nv">$NEW_VERSION</span>/RC<span class="nv">$RELEASE_CANDIDATE</span>/apache-sis-<span
class="nv">$NEW_VERSION</span> <span class="se">\</span>
                   <span class="nv">$NEW_VERSION</span>/RC<span
class="nv">$RELEASE_CANDIDATE</span>/apache-sis-<span class="nv">$NEW_VERSION</span>
@@ -519,7 +530,7 @@ bin/sis metadata
-<h1 id="vote">Put the release candidate up for a vote</h1>
+<h1 id="vote">Put the release candidate up for a vote<a class="headerlink" href="#vote"
title="Permanent link">&para;</a></h1>
 <li>Create a VOTE email thread on <code>dev@</code> to record votes as
     A template is available <a href="templates/release-vote.txt">here</a>.</li>
@@ -535,7 +546,7 @@ bin/sis metadata
-<h2 id="veto">Recovering from a vetoed release</h2>
+<h2 id="veto">Recovering from a vetoed release<a class="headerlink" href="#veto"
title="Permanent link">&para;</a></h2>
 <p>Reply to the initial vote email and prepend to the original subject:</p>
 <div class="codehilite"><pre>[CANCELED]
@@ -552,7 +563,7 @@ bin/sis metadata
 <li>Right click on the closed staging repositories (<code>org.apache.sis-&lt;id&gt;</code>)
and select <em>Drop</em>.</li>
 <p>Make the required updates that caused the vote to be canceled during the release
-<h1 id="finalize">Finalize the release</h1>
+<h1 id="finalize">Finalize the release<a class="headerlink" href="#finalize" title="Permanent
 <p>The artificats in the repository are not yet mirrored and available for Maven to
 Promote the staged Nexus artifacts, by releasing them.</p>
@@ -581,14 +592,14 @@ svn delete
-<h2 id="verify">Verify release signatures</h2>
+<h2 id="verify">Verify release signatures<a class="headerlink" href="#verify" title="Permanent
 <p>Download all source and binary artifacts into a new directory, then execute in that
 <div class="codehilite"><pre>find . -name <span class="s2">&quot;*.asc&quot;</span>
-exec gpg --verify <span class="s1">&#39;{}&#39;</span> <span class="se">\;</span>
 <p>The output shall report only good signatures.</p>
-<h2 id="announce">Announce the release</h2>
+<h2 id="announce">Announce the release<a class="headerlink" href="#announce" title="Permanent
 <li>WAIT 24 hours after committing releases for mirrors to replicate.</li>
 <li>Publish the web site updates:<ul>
@@ -606,7 +617,7 @@ svn delete
-<h1 id="next-release">Update trunk for the next development cycle</h1>
+<h1 id="next-release">Update trunk for the next development cycle<a class="headerlink"
href="#next-release" title="Permanent link">&para;</a></h1>
 <p>On the development branch (usually JDK8),
 update the version numbers in the <code>pom.xml</code> files on trunk with the
following command:</p>
 <div class="codehilite"><pre>mvn clean
@@ -621,7 +632,7 @@ Then on the development branch:</p>
 <li>Edit the value of the <code>MAJOR_VERSION</code> or <code>MINOR_VERSION</code>
constant in the
-<h2 id="nexus-clean">Delete old artifacts on Maven snapshot repository</h2>
+<h2 id="nexus-clean">Delete old artifacts on Maven snapshot repository<a class="headerlink"
href="#nexus-clean" title="Permanent link">&para;</a></h2>
 <p>Login in the <a href="">Nexus repository</a>.
In the <em>Repositories</em> tag, select <em>Snapshots</em> of type
 (not to be confused with <em>Snapshots</em> of type <em>group</em>).
Navigate to the <code>org/apache/sis</code> directory and delete
 all directories starting with the old version number. The sub-directories need to be cleaned

Modified: websites/staging/sis/trunk/content/release-notes/0.5.html
--- websites/staging/sis/trunk/content/release-notes/0.5.html (original)
+++ websites/staging/sis/trunk/content/release-notes/0.5.html Fri Sep 11 17:36:33 2015
@@ -7,7 +7,7 @@
     <table style="border-style: solid; border-width: 1pt; background: lightgray"><tr>
       <td><a href="0.4.html">Previous release</a></td>
-      <td style="padding-left: 9pt">Next release</td>
+      <td style="padding-left: 9pt"><a href="0.6.html">Next release</a></td>
     <h1>SIS 0.5 Release notes</h1>

Added: websites/staging/sis/trunk/content/release-notes/0.6.html
--- websites/staging/sis/trunk/content/release-notes/0.6.html (added)
+++ websites/staging/sis/trunk/content/release-notes/0.6.html Fri Sep 11 17:36:33 2015
@@ -0,0 +1,83 @@
+<!DOCTYPE html>
+<html lang="en">
+  <head>
+    <title>SIS 0.6 Release notes</title>
+    <meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
+  </head>
+  <body>
+    <table style="border-style: solid; border-width: 1pt; background: lightgray"><tr>
+      <td><a href="0.5.html">Previous release</a></td>
+      <td style="padding-left: 9pt">Next release</td>
+    </tr></table>
+    <h1>SIS 0.6 Release notes</h1>
+<p>The main new feature of Apache SIS 0.6 are:</p>
+  <li>Support of <cite>Well Known Text</cite> version 1 and 2 (a.k.a ISO
19162) for Coordinate Reference System objects.</li>
+  <li>Support of <cite>Geographic Markup Language</cite> (GML) for Coordinate
Reference System objects,
+    except <code>DerivedCRS</code>, <code>ConcatenatedOperation</code>
and <code>PassThroughOperation</code>.</li>
+  <li>Support of <cite>Mercator</cite>, <cite>Transverse Mercator</cite>,
<cite>Lambert Conformal Conical</cite>
+      and <cite>Polar stereographic</cite> map projections.</li>
+<p>The list of map projection methods supported by latest SIS release can be viewed
+  <a href="../content/CoordinateOperationMethods.html">here</a>.</p>
+<h2>New features</h2>
+  <li>[<a href=''>SIS-8</a>]
- Build a common SIS data container for spatial data</li>
+  <li>[<a href=''>SIS-9</a>]
- Allow for multiple spatial reference systems</li>
+  <li>[<a href=''>SIS-285</a>]
- Make OSGi compatible</li>
+  <li>[<a href=''>SIS-234</a>]
- Equidistant Cylindrical (Spherical) (EPSG:1029)</li>
+  <li>[<a href=''>SIS-239</a>]
- Lambert Conic Conformal 2SP (EPSG:9802)</li>
+  <li>[<a href=''>SIS-240</a>]
- Lambert Conic Conformal 1SP (EPSG:9801)</li>
+  <li>[<a href=''>SIS-241</a>]
- Lambert Conic Conformal West Orientated (EPSG:9826)</li>
+  <li>[<a href=''>SIS-242</a>]
- Lambert Conic Conformal Belgium (EPSG:9803)</li>
+  <li>[<a href=''>SIS-243</a>]
- Lambert Conic Conformal Michigan (EPSG:1051)</li>
+  <li>[<a href=''>SIS-244</a>]
- Mercator variant A (EPSG:9804)</li>
+  <li>[<a href=''>SIS-245</a>]
- Mercator variant B (EPSG:9805)</li>
+  <li>[<a href=''>SIS-246</a>]
- Mercator variant C (EPSG:1044)</li>
+  <li>[<a href=''>SIS-247</a>]
- Mercator (Spherical) (EPSG:1026)</li>
+  <li>[<a href=''>SIS-248</a>]
- Popular Visualisation Pseudo Mercator (EPSG:1024)</li>
+  <li>[<a href=''>SIS-251</a>]
- Polar Stereographic variant A (EPSG:9810)</li>
+  <li>[<a href=''>SIS-252</a>]
- Polar Stereographic variant B (EPSG:9829)</li>
+  <li>[<a href=''>SIS-253</a>]
- Polar Stereographic variant C (EPSG:9830)</li>
+  <li>[<a href=''>SIS-264</a>]
- Affine Parametric Transformation (EPSG:9624)</li>
+  <li>[<a href=''>SIS-33</a>]
- Make SIS data storage pluggable</li>
+  <li>[<a href=''>SIS-165</a>]
- Add an AngleRange class for latitude/longitude ranges</li>
+  <li>[<a href=''>SIS-184</a>]
- DBase 3 - JDBC : Simple WHERE CLAUSE and Integer, Double field support</li>
+  <li>[<a href=''>SIS-201</a>]
- Citations.getIdentifier(Citation) should take Identifier.codeSpace in account</li>
+  <li>[<a href=''>SIS-288</a>]
- Implement projection derivative for TransverseMercator</li>
+<h2>Bug fixes</h2>
+  <li>[<a href=''>SIS-192</a>]
- Suppression of &quot;3.2&quot; in &quot;;
does not work</li>
+  <li>[<a href=''>SIS-194</a>]
- DefaultResolution.isEmpty() and prune() do not detect when RepresentativeFraction is empty</li>
+  <li>[<a href=''>SIS-195</a>]
- DefaultResolution(RepresentativeFraction) constructor does not correctly store the given
+  <li>[<a href=''>SIS-197</a>]
- Remove the scope of NamedIdentifier, since it duplicates the path</li>
+  <li>[<a href=''>SIS-199</a>]
- Resolve confusion between EPSG and IOGP in Citations</li>
+  <li>[<a href=''>SIS-200</a>]
- Citations should not provide constant for organisations</li>
+  <li>[<a href=''>SIS-202</a>]
- Parameters.copy(...) does not traverse subgroups correctly</li>
+  <li>[<a href=''>SIS-287</a>]
- TransverseMercator projection provider missing in service file</li>
+  <li>[<a href=''>SIS-297</a>]
- Enum value lost at unmarshalling time if the name is composed of more than one word</li>
+  <li>[<a href=''>SIS-166</a>]
- Replace repetition of private getter/setters in CRS classes by @XmlElements annotation</li>
+  <li>[<a href=''>SIS-196</a>]
- OGP organization has been renamed IOGP</li>
+  <li>[<a href=''>SIS-198</a>]
- Remove &quot;remarks&quot; property from ImmutableIdentifier (replaced by &quot;description&quot;)</li>
+  <li>[<a href=''>SIS-204</a>]
- Verify CompoundCRS restrictions at format time</li>
+  <li>[<a href=''>SIS-205</a>]
- Enforce character encoding restriction at format time</li>
+  <li>[<a href=''>SIS-208</a>]
- Support explicit Order element in axes</li>
+  <li>[<a href=''>SIS-290</a>]
- Complete JAXB annotations for OperationParameter and ParameterValue</li>
+  <li>[<a href=''>SIS-291</a>]
- Complete JAXB annotations for SingleOperation</li>
+  </body>

View raw message