sis-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r1050175 - in /websites/staging/sis/trunk/content: ./ downloads.html mail-lists.html release-management-setup.html release-management.html
Date Mon, 16 Sep 2019 16:45:05 GMT
Author: buildbot
Date: Mon Sep 16 16:45:04 2019
New Revision: 1050175

Log:
Staging update by buildbot for sis

Modified:
    websites/staging/sis/trunk/content/   (props changed)
    websites/staging/sis/trunk/content/downloads.html
    websites/staging/sis/trunk/content/mail-lists.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 Mon Sep 16 16:45:04 2019
@@ -1 +1 @@
-1867002
+1867020

Modified: websites/staging/sis/trunk/content/downloads.html
==============================================================================
--- websites/staging/sis/trunk/content/downloads.html (original)
+++ websites/staging/sis/trunk/content/downloads.html Mon Sep 16 16:45:04 2019
@@ -127,7 +127,7 @@ in a classpath.</p>
 <h2 id="release-gpg">Verify signatures<a class="headerlink" href="#release-gpg"
title="Permanent link">&para;</a></h2>
 <p>All downloads can be verified using the Apache SIS code signing <a href="http://www.apache.org/dist/sis/KEYS">KEYS</a>.
 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.
+First download the <a href="http://www.apache.org/dist/sis/KEYS">KEYS</a> file
and the <code>.asc</code> signature files for the relevant release packages.
 Make sure you get these files from the main distribution directory, rather than from a mirror.
 Then verify the signatures using the following:</p>
 <p>Using GNU Privacy Guard:</p>
@@ -152,7 +152,7 @@ pgpv apache-sis-X.Y.Z.zip.asc
 <p>An easy approach to integrate Apache SIS into a Java project uses the <a href="http://maven.apache.org/">Apache
Maven</a>
 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 a SIS core module.
-If running on Java 11 or higher, <em>one</em> of the two next dependencies is
also required:</p>
+If running on Java 11 or higher, at least one of the two next dependencies is also required:</p>
 <div class="codehilite"><pre><span class="nt">&lt;properties&gt;</span>
   <span class="nt">&lt;sis.version&gt;</span>0.8<span class="nt">&lt;/sis.version&gt;</span>
 <span class="nt">&lt;/properties&gt;</span>

Modified: websites/staging/sis/trunk/content/mail-lists.html
==============================================================================
--- websites/staging/sis/trunk/content/mail-lists.html (original)
+++ websites/staging/sis/trunk/content/mail-lists.html Mon Sep 16 16:45:04 2019
@@ -121,8 +121,8 @@ or collaboration with communities outsid
 <li>Post (after subscription): <a href="mailto:user@sis.apache.org">user@sis.apache.org</a></li>
 <li>Unsubscribe: <a href="mailto:user-unsubscribe@sis.apache.org">user-unsubscribe@sis.apache.org</a></li>
 <li>Archives:<ul>
-<li><a href="http://mail-archives.apache.org/mod_mbox/sis-user/">Apache</a></li>
 <li><a href="https://lists.apache.org/list.html?user@sis.apache.org">Pony mail</a></li>
+<li><a href="http://mail-archives.apache.org/mod_mbox/sis-user/">Apache</a></li>
 </ul>
 </li>
 </ul>
@@ -133,8 +133,8 @@ or collaboration with communities outsid
 <li>Post (after subscription): <a href="mailto:dev@sis.apache.org">dev@sis.apache.org</a></li>
 <li>Unsubscribe: <a href="mailto:dev-unsubscribe@sis.apache.org">dev-unsubscribe@sis.apache.org</a></li>
 <li>Archives:<ul>
-<li><a href="http://mail-archives.apache.org/mod_mbox/sis-dev/">Apache</a></li>
 <li><a href="https://lists.apache.org/list.html?dev@sis.apache.org">Pony mail</a></li>
+<li><a href="http://mail-archives.apache.org/mod_mbox/sis-dev/">Apache</a></li>
 </ul>
 </li>
 </ul>
@@ -145,8 +145,8 @@ any changes to the sis code and document
 <li>Subscribe: <a href="mailto:commits-subscribe@sis.apache.org">commits-subscribe@sis.apache.org</a></li>
 <li>Unsubscribe: <a href="mailto:commits-unsubscribe@sis.apache.org">commmits-unsubscribe@sis.apache.org</a></li>
 <li>Archives:<ul>
-<li><a href="http://mail-archives.apache.org/mod_mbox/sis-commits/">Apache</a></li>
 <li><a href="https://lists.apache.org/list.html?commits@sis.apache.org">Pony
mail</a></li>
+<li><a href="http://mail-archives.apache.org/mod_mbox/sis-commits/">Apache</a></li>
 </ul>
 </li>
 </ul>

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 Mon Sep 16 16:45:04 2019
@@ -118,8 +118,6 @@ Some directories are Git checkout, other
 However in the later case, all relative paths in the <em>release management</em>
page will need to be adjusted accordingly.</p>
 <div class="codehilite"><pre>&lt;any root directory for SIS&gt;
 ├─ master
-├─ branches
-├─ tags
 ├─ non-free
 │  ├─ sis-epsg
 │  └─ sis-embedded-data
@@ -136,8 +134,6 @@ svn checkout https://svn.apache.org/repo
 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
-mkdir branches
-mkdir tags
 </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 Mon Sep 16 16:45:04 2019
@@ -106,12 +106,10 @@ The intended audiences are SIS release m
 <ul>
 <li><a href="#configure">Configure</a><ul>
 <li><a href="#directory-layout">Directory layout</a></li>
-<li><a href="#java-version">Java versions</a></li>
 </ul>
 </li>
-<li><a href="#prepare-source">Prepare web site and source code before branching</a><ul>
+<li><a href="#prepare-source">Review project status before branching</a><ul>
 <li><a href="#release-notes">Prepare release notes</a></li>
-<li><a href="#prepare-website">Web site</a></li>
 <li><a href="#test-master">Test master extensively</a></li>
 <li><a href="#prepare-code">Source code</a></li>
 </ul>
@@ -135,6 +133,7 @@ The intended audiences are SIS release m
 </ul>
 </li>
 <li><a href="#openoffice">Prepare OpenOffice add-in</a></li>
+<li><a href="#prepare-website">Prepare Web site</a></li>
 <li><a href="#vote">Put the release candidate up for a vote</a><ul>
 <li><a href="#veto">Recovering from a vetoed release</a></li>
 </ul>
@@ -154,7 +153,7 @@ The intended audiences are SIS release m
 <p>Before to perform a release, make sure that the following conditions hold:</p>
 <ul>
 <li>Commands will be executed in a Unix shell.</li>
-<li>Subversion, GNU GPG, ZIP, Maven, Ant, Java and the Java compiler are available
on the path.</li>
+<li>Git, Subversion, GNU GPG, ZIP, Maven, Ant, Java and the Java compiler are available
on the path.</li>
 <li>The <a href="release-management-setup.html">release management setup</a>
steps have been executed once.</li>
 </ul>
 <p>For all instructions in this page, <code>$OLD_VERSION</code> and <code>$NEW_VERSION</code>
stand for the version
@@ -164,17 +163,12 @@ the current release attempt. Those versi
 <span class="nb">export </span><span class="nv">NEW_VERSION</span><span
class="o">=</span>1.0
 <span class="nb">export </span><span class="nv">RELEASE_CANDIDATE</span><span
class="o">=</span>1
 <span class="nb">export </span><span class="nv">SIGNING_KEY</span><span
class="o">=</span>&lt;your key ID&gt;
-<span class="nb">export </span><span class="nv">BOOTCLASSPATH</span><span
class="o">=</span>&lt;path to the rt.jar file of a JDK7 installation&gt;
+<span class="nb">unset </span>PATH_TO_FX
 </pre></div>
 
 
 <p>The key ID value is an hexadecimal numbers with 8 digits (may be the last 8 digits
of a 40 digits number).
 It can be found be executing <code>gpg --list-keys</code>.</p>
-<p>The boot class path value is highly system-dependent. Some examples are:</p>
-<ul>
-<li><code>/usr/lib/jvm/java-7/jre/lib/rt.jar</code> on some Linux distributions
(replace <code>java-7</code> by the actual directory name).</li>
-<li><code>/Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/jre/lib/rt.jar</code>
on MacOS.</li>
-</ul>
 <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.</p>
 <div class="codehilite"><pre><span class="nb">eval</span> <span
class="k">$(</span>gpg-agent --daemon<span class="k">)</span>
@@ -187,12 +181,6 @@ a result of the steps). Any other layout
 in this page shall be adjusted accordingly.</p>
 <div class="codehilite"><pre>&lt;any root directory for SIS&gt;
 ├─ master
-├─ branches
-│  └─ $NEW_VERSION
-├─ tags
-│  └─ $NEW_VERSION
-│     └─ target
-│        └─ distributions
 ├─ non-free
 │  └─ sis-epsg
 ├─ distribution
@@ -204,13 +192,7 @@ in this page shall be adjusted according
 </pre></div>
 
 
-<h2 id="java-version">Java versions<a class="headerlink" href="#java-version" title="Permanent
link">&para;</a></h2>
-<p>While we need a JDK7 installation for the <code>bootclasspath</code>
option, we do not recommend to use it for generating
-the binaries since JDK7 has reached its end of public updates (but not the end of commercial
support).
-We recommend to create the release with JDK8 instead (note however that JDK8 <code>javadoc</code>
tool seems to have a bug that prevent its use with SIS).
-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 web site and source code before branching<a class="headerlink"
href="#prepare-source" title="Permanent link">&para;</a></h1>
+<h1 id="prepare-source">Review project status before branching<a class="headerlink"
href="#prepare-source" title="Permanent link">&para;</a></h1>
 <p>Before to start the release process, we need to test more extensively the master.
 The tests described below often reveal errors that were unnoticed in daily builds.
 It is better to detect and fix them before to create the branch.
@@ -218,40 +200,33 @@ First:</p>
 <ul>
 <li>Review and update the <code>README</code> and <code>NOTICE</code>
files on the 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>
+<p>Tests the following commands:</p>
+<p>:::bash
+mvn clean install --define org.apache.sis.test.extensive=true
+mvn javadoc::aggregate</p>
+</li>
 </ul>
 <h2 id="release-notes">Prepare release notes<a class="headerlink" href="#release-notes"
title="Permanent link">&para;</a></h2>
-<p>We update JIRA first because doing so is sometime a reminder of uncompleted tasks
in source code.
+<p>We update JIRA soon because doing so is sometime a reminder of uncompleted tasks
in source code.
 Update <a href="http://issues.apache.org/jira/browse/SIS">JIRA</a> tasks and
prepare release notes as below:</p>
 <ul>
 <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>
tags.</li>
-<li>The release notes can be obtained from JIRA, by clicking on the <em>Roadmap</em>
tab → the version number → <em>Release notes</em>
+<li>The release notes can be obtained from JIRA, by clicking on the <em>Versions</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>
 </ul>
-<h2 id="prepare-website">Web site<a class="headerlink" href="#prepare-website" title="Permanent
link">&para;</a></h2>
-<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>
-<ul>
-<li><code>content/index.mdtext</code></li>
-<li><code>content/gdal.mdtext</code></li>
-<li><code>content/downloads.mdtext</code> (need also to update <code>$NEW_VERSION-SNAPSHOT</code>
to the next snapshot version)</li>
-<li><code>content/command-line.mdtext</code></li>
-<li><code>content/epsg.mdtext</code> (be aware that the version number
may sometime be behind the SIS version number)</li>
-</ul>
-<p>Commit:</p>
+<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
-svn commit --message <span class="s2">&quot;Prepare documentation for the $NEW_VERSION
release.&quot;</span>
+svn commit --message <span class="s2">&quot;Release notes for Apache SIS $NEW_VERSION.&quot;</span>
 </pre></div>
 
 
-<p>The new web site will be published in the <a href="http://sis.staging.apache.org">staging
area</a>.
-It will not yet be published on <code>http://sis.apache.org</code>.</p>
 <h2 id="test-master">Test master extensively<a class="headerlink" href="#test-master"
title="Permanent link">&para;</a></h2>
 <p>Build the project with the <code>apache-release</code> profile enabled.
 This profile performs the following actions:</p>
@@ -264,8 +239,7 @@ This profile performs the following acti
 <li>Sign the artifacts.</li>
 </ul>
 <p>Each of those additional products may cause a failure that did not happen in normal
builds.</p>
-<div class="codehilite"><pre><span class="nb">cd</span> ../master
-mvn clean install --activate-profiles apache-release --define <span class="nv">bootclasspath</span><span
class="o">=</span><span class="nv">$BOOTCLASSPATH</span>
+<div class="codehilite"><pre>mvn clean install --activate-profiles apache-release
 </pre></div>
 
 
@@ -281,7 +255,7 @@ but we nevertheless need to ensure that
 SIS dependencies are the snapshot tested in this section.</p>
 <div class="codehilite"><pre><span class="nb">cd</span> ../non-free
 svn update
-mvn clean install --define <span class="nv">bootclasspath</span><span class="o">=</span><span
class="nv">$BOOTCLASSPATH</span>
+mvn clean install
 </pre></div>
 
 
@@ -291,7 +265,7 @@ Note that execution of those tests may b
 <div class="codehilite"><pre><span class="nb">cd</span> ../release-test
 svn update
 <span class="nb">cd </span>maven
-mvn clean <span class="nb">test</span> --define <span class="nv">bootclasspath</span><span
class="o">=</span><span class="nv">$BOOTCLASSPATH</span>
+mvn clean <span class="nb">test</span>
 </pre></div>
 
 
@@ -343,7 +317,7 @@ git rm application/sis-javafx
 
 <p>Validate with <code>git diff</code>, ensure that the build is not broken
(we will run the tests later),
 then commit the changes on the branch:</p>
-<div class="codehilite"><pre>mvn clean package --define <span class="nv">skipTests</span><span
class="o">=</span><span class="nb">true</span> --define <span class="nv">bootclasspath</span><span
class="o">=</span><span class="nv">$BOOTCLASSPATH</span>
+<div class="codehilite"><pre>mvn clean package --define <span class="nv">skipTests</span><span
class="o">=</span><span class="nb">true</span>
 git commit --message <span class="s2">&quot;Prepare branch for $NEW_VERSION release.&quot;</span>
 </pre></div>
 
@@ -381,7 +355,7 @@ plus some additional files:</p>
 <h2 id="branch-verify">Verify content<a class="headerlink" href="#branch-verify"
title="Permanent link">&para;</a></h2>
 <p>Build and test the project in the same way than we did on master.
 In addition to testing, execution of an <code>install</code> phase before deployment
is required for our custom <code>sis-build-helper</code> plugin.</p>
-<div class="codehilite"><pre>mvn install --activate-profiles apache-release --define
<span class="nv">bootclasspath</span><span class="o">=</span><span
class="nv">$BOOTCLASSPATH</span>
+<div class="codehilite"><pre>mvn install --activate-profiles apache-release
 find . -name <span class="s2">&quot;sis-*.asc&quot;</span> -exec gpg
--verify <span class="s1">&#39;{}&#39;</span> <span class="se">\;</span>
 </pre></div>
 
@@ -393,7 +367,7 @@ Create tags and trunk directories.
 Commit and built:</p>
 <div class="codehilite"><pre><span class="nb">cd</span> ../../non-free
 svn commit --message <span class="s2">&quot;Set version number and dependencies
to $NEW_VERSION.&quot;</span>
-mvn clean install --define <span class="nv">bootclasspath</span><span class="o">=</span><span
class="nv">$BOOTCLASSPATH</span>
+mvn clean install
 </pre></div>
 
 
@@ -403,14 +377,14 @@ Commit and built (note that execution ma
 <div class="codehilite"><pre><span class="nb">cd</span> ../release-test
 svn commit --message <span class="s2">&quot;Set version number and dependencies
to $NEW_VERSION.&quot;</span>
 <span class="nb">cd </span>maven
-mvn clean <span class="nb">test</span> --define <span class="nv">bootclasspath</span><span
class="o">=</span><span class="nv">$BOOTCLASSPATH</span>
+mvn clean <span class="nb">test</span>
 </pre></div>
 
 
 <h1 id="maven-deploy">Deploy Maven artifacts<a class="headerlink" href="#maven-deploy"
title="Permanent link">&para;</a></h1>
 <p>If above verifications succeeded, deploy:</p>
 <div class="codehilite"><pre>chmod a-w target/distribution/*.zip
-mvn deploy --activate-profiles apache-release --define <span class="nv">bootclasspath</span><span
class="o">=</span><span class="nv">$BOOTCLASSPATH</span>
+mvn deploy --activate-profiles apache-release
 </pre></div>
 
 
@@ -449,7 +423,7 @@ before deployment of the rest of Apache
 <p>Go to the directory that contains a checkout of <code>https://svn.apache.org/repos/asf/sis/data/non-free/sis-epsg</code>.
 Replace occurrences of <code>&lt;version&gt;$OLD_VERSION&lt;/version&gt;</code>
by <code>&lt;version&gt;$NEW_VERSION&lt;/version&gt;</code> in
the root <code>pom.xml</code>.
 Deploy:</p>
-<div class="codehilite"><pre>mvn deploy --activate-profiles apache-release --define
<span class="nv">bootclasspath</span><span class="o">=</span><span
class="nv">$BOOTCLASSPATH</span>
+<div class="codehilite"><pre>mvn deploy --activate-profiles apache-release
 </pre></div>
 
 
@@ -629,6 +603,24 @@ to build the add-in:</p>
     A copy is found in the <code>non-free</code> group of SIS modules.</li>
 <li>Run <code>mvn package --activate-profiles non-free</code>.</li>
 </ul>
+<h1 id="prepare-website">Prepare Web site<a class="headerlink" href="#prepare-website"
title="Permanent link">&para;</a></h1>
+<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>
+<ul>
+<li><code>content/index.mdtext</code></li>
+<li><code>content/gdal.mdtext</code></li>
+<li><code>content/downloads.mdtext</code> (need also to update <code>$NEW_VERSION-SNAPSHOT</code>
to the next snapshot version)</li>
+<li><code>content/command-line.mdtext</code></li>
+<li><code>content/epsg.mdtext</code> (be aware that the version number
may sometime be behind the SIS version number)</li>
+</ul>
+<p>Commit:</p>
+<div class="codehilite"><pre>svn commit --message <span class="s2">&quot;Prepare
documentation for the $NEW_VERSION release.&quot;</span>
+</pre></div>
+
+
+<p>The new web site will be published in the <a href="http://sis.staging.apache.org">staging
area</a>.
+It will not yet be published on <code>http://sis.apache.org</code>.</p>
 <h1 id="vote">Put the release candidate up for a vote<a class="headerlink" href="#vote"
title="Permanent link">&para;</a></h1>
 <ul>
 <li>Create a VOTE email thread on <code>dev@</code> to record votes as
replies.



Mime
View raw message