sis-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r939109 - in /websites/staging/sis/trunk/content: ./ release-management.html
Date Thu, 05 Feb 2015 15:00:16 GMT
Author: buildbot
Date: Thu Feb  5 15:00:16 2015
New Revision: 939109

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 Thu Feb  5 15:00:16 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 Thu Feb  5 15:00:16 2015
@@ -90,6 +90,7 @@ The intended audiences are SIS release m
 <li><a href="#requirements">Requirements</a><ul>
 <li><a href="#directory-layout">Directory layout</a></li>
+<li><a href="#java-update">Java updates</a></li>
 <li><a href="#prepare-source">Prepare site and source code</a><ul>
@@ -147,6 +148,7 @@ the current release attempt. Those versi
 <p>The key ID value can be found be executing <code>gpg --list-keys</code>.
 The boot class path value is highly system-dependent. Some examples are:</p>
+<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>
@@ -170,6 +172,12 @@ in this page shall be adjusted according
+<h2 id="java-update">Java updates</h2>
+<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>
 <p>Before to start the release process:</p>
@@ -236,8 +244,10 @@ but also in a few Java files. The follow
 <p>In <code>core/sis-utility/src/main/java/org/apache/sis/internal/system/</code>,
consider setting
 the <code>ENABLED</code> flag to <code>false</code>. This policy
may be revised in future SIS releases.</p>
-<p>Remove the workaround for the bug in JDK6 <code>javadoc</code>, since
we perform release with JDK7 or JDK8:</p>
+<p>Remove the workaround for the bug in JDK6 <code>javadoc</code>, since
we perform release with JDK7 or JDK8.
+Remove also the modules that are not yet ready for a release:</p>
 <div class="codehilite"><pre>svn remove core/sis-build-helper/src/main/java/org/opengis
+svn remove application/sis-javafx
@@ -314,8 +324,7 @@ ignoring the license or other informatio
 <p>Clean the branch, since we will not need it anymore:</p>
 <div class="codehilite"><pre><span class="nb">cd</span> <span
-mvn release:clean
-mvn clean
+mvn clean release:clean
@@ -325,7 +334,7 @@ and generate the binary artifact (<code>
 class files or resources are found. Consequently building the <code>pack.gz</code>
file is an
 additional test worth to do before deployment.</p>
 <div class="codehilite"><pre><span class="nb">cd</span> <span
-mvn clean install
+mvn clean install --define <span class="nv">bootclasspath</span><span class="o">=</span><span
 mvn org.apache.sis.core:sis-build-helper:<span class="nv">$NEW_VERSION</span>:dist
@@ -334,7 +343,7 @@ mvn org.apache.sis.core:sis-build-helper
 for preventing Maven to deploy them, since there is no apparent reason why users would want
 download site descriptors from a Maven repository.</p>
 <div class="codehilite"><pre>find . -name <span class="s2">&quot;site.xml&quot;</span>
-mvn deploy --activate-profiles apache-release
+mvn deploy --activate-profiles apache-release --define <span class="nv">bootclasspath</span><span
class="o">=</span><span class="nv">$BOOTCLASSPATH</span>
 svn revert . --recursive
@@ -361,7 +370,7 @@ so try to see at least one code snippet.
 <p>Close the Nexus staging repository:</p>
 <li>Click the checkboxes for the open staging repositories (<code>org.apache.sis-&lt;id&gt;</code>)
and press <em>Close</em> in the menu bar.</li>
-<li>In the description field, enter "<code>SIS $NEW_VERSION-$RELEASE_CANDIDATE</code>"
+<li>In the description field, enter "<code>SIS $NEW_VERSION-RC$RELEASE_CANDIDATE</code>"
     (replace <code>$NEW_VERSION</code> and <code>$RELEASE_CANDIDATE</code>
by appropriate values.
     This will not be done automatically since this field box is not our bash shell!).</li>
 <li>Click on the <code>org.apache.sis-&lt;id&gt;</code> link in
order to get the URL to the temporary Maven repository created by Nexus.</li>
@@ -369,9 +378,11 @@ 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>
-<p>Go to the test Maven project. Open the root <code>pom.xml</code> file,
go to the <code>&lt;url&gt;</code> declaration and replace value by
-the URL of the temporary Maven repository created by Nexus. Usually, only the 3 last digits
need to be updated.
-Set the <code>&lt;version&gt;</code> number to the SIS release to be
+<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
+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
 svn commit -m <span class="s2">&quot;Test project for SIS $NEW_VERSION-RC$RELEASE_CANDIDATE&quot;</span>
@@ -382,6 +393,7 @@ svn commit -m <span class="s2">&quot;Tes
 This will also verify the checksums.</p>
 <div class="codehilite"><pre><span class="n">rm</span> <span class="o">-</span><span
class="n">r</span> <span class="o">~/</span><span class="p">.</span><span
class="n">m2</span><span class="o">/</span><span class="n">repository</span><span
class="o">/</span><span class="n">org</span><span class="o">/</span><span
class="n">apache</span><span class="o">/</span><span class="n">sis</span>
 <span class="n">mvn</span> <span class="n">package</span> <span
class="o">--</span><span class="n">strict</span><span class="o">-</span><span
+<span class="n">mvn</span> <span class="n">clean</span>
@@ -392,7 +404,7 @@ avoiding the security vulnerability disc
 and keeping the <code>diff</code> smaller on the SVN repository of SIS web site.
 If JDK8 is <em>not</em> used, then omit the <code>cp</code> command
 <div class="codehilite"><pre>cp ../../JDK8/src/main/javadoc/stylesheet.css src/main/javadoc/
-mvn site --define <span class="nv">skipTests</span><span class="o">=</span><span
+mvn javadoc:aggregate --define <span class="nv">bootclasspath</span><span
class="o">=</span><span class="nv">$BOOTCLASSPATH</span>
 svn revert src/main/javadoc/stylesheet.css
 <span class="nb">cd </span>target/site
 zip -9 -r apache-sis-<span class="nv">$NEW_VERSION</span> apidocs

View raw message