sis-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r871014 - in /websites/staging/sis/trunk/content: ./ downloads.html release-management.html
Date Wed, 24 Jul 2013 16:33:04 GMT
Author: buildbot
Date: Wed Jul 24 16:33:04 2013
New Revision: 871014

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 Jul 24 16:33:04 2013
@@ -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 Jul 24 16:33:04 2013
@@ -81,7 +81,10 @@
 See the <code>NOTICE</code> file contained in each release artifact for applicable
copyright attribution notices.</p>
 <div class="toc">
-<li><a href="#download-zipgz-files">Download ZIP/GZ files</a></li>
+<li><a href="#download-zipgz-files">Download ZIP/GZ files</a><ul>
+<li><a href="#release-notes">Release notes</a></li>
 <li><a href="#download-as-a-maven-dependency">Download as a Maven dependency</a><ul>
 <li><a href="#using-sis-releases">Using SIS releases</a></li>
 <li><a href="#using-sis-development-snapshots">Using SIS development snapshots</a></li>
@@ -120,6 +123,8 @@ pgpv apache-sis-X.Y.Z.tar.gz.asc
+<h2 id="release-notes">Release notes</h2>
+<p>See the [release notes][release-notes/0.2.html] for a list of changes since the
previous version.</p>
 <h1 id="download-as-a-maven-dependency">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.

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 Jul 24 16:33:04 2013
@@ -86,10 +86,14 @@ The intended audiences are SIS release m
 <li><a href="#directory-layout">Directory layout</a></li>
-<li><a href="#prepare-documentation">Prepare documentation</a></li>
-<li><a href="#prepare-the-web-site">Prepare the web site</a></li>
-<li><a href="#create-a-branch">Create a branch</a></li>
-<li><a href="#verify-the-branch-content">Verify the branch content</a></li>
+<li><a href="#prepare-documentation">Prepare documentation</a><ul>
+<li><a href="#web-site">Web site</a></li>
+<li><a href="#create-a-branch">Create a branch</a><ul>
+<li><a href="#verify-content">Verify content</a></li>
 <li><a href="#deploy-the-release">Deploy the release</a></li>
 <li><a href="#verify-and-close-the-nexus-release-artifacts">Verify and close
the Nexus release artifacts</a></li>
 <li><a href="#stage-the-binary-and-javadoc-artifacts-to-the-distribution-development-repository">Stage
the binary and javadoc artifacts to the distribution development repository</a></li>
@@ -144,19 +148,18 @@ in this page shall be adjusted according
 <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>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>
-<li>Review and update the <code>README</code> file.</li>
-<li>Commit any changes back to SVN.</li>
-<li>Update the following Wiki pages:<ul>
+<p>Other files to update:</p>
+<li>Review and update the <code>README</code> file on the <code>trunk</code>
source code repository.</li>
+<li>Commit any changes back to SVN.</li>
-<h1 id="prepare-the-web-site">Prepare the web site</h1>
+<h2 id="web-site">Web site</h2>
 <p>Update the version numbers from <code>$NEW_VERSION</code> to the next
version in the following files.</p>
@@ -204,7 +207,7 @@ the <code>ENABLED</code> flag to <code>f
-<h1 id="verify-the-branch-content">Verify the branch content</h1>
+<h2 id="verify-content">Verify content</h2>
 <p>Try a dry run of the <code>release:prepare</code> goal. This goals checks
for <code>SNAPSHOT</code> dependencies in <code>pom.xml</code> files.
 It will not complete the prepare goal until all <code>SNAPSHOT</code> dependencies
are resolved.
 If anything goes wrong, the directory can be cleaned by running the <code>release:clean</code>
@@ -394,13 +397,17 @@ Promote the staged Nexus artifacts, by r
 <li>Delete the prior release artifacts using the <code>svn delete</code>
 <li>Commit the deletion.</li>
-<p>Update the JIRA versions page to close all issues, mark the version as "released",
+<p>Update the <a href="">JIRA</a>
versions to mark the version as "released",
 and set the date to the date that the release was approved.
-Make a new release entry for the next release.</p>
+Then prepare for the next release:</p>
+<li>Make a new release entry in JIRA for the next release.</li>
+<li>Update the <a href="">Roadmap</a>
wiki page.</li>
 <h2 id="announce-the-release">Announce the release</h2>
 <li>Make a news announcement on the SIS home page.</li>
-<li>Make an announcement about the release on the <code>dev@</code>, <code>users@,
and</code>announce@` mailing lists.<ul>
+<li>Make an announcement about the release on the <code>dev@</code>, <code>users@</code>,
and <code>announce@</code> mailing lists.<ul>
 <li>Sample announce: <a href="release-announce.txt">email</a>.</li>

View raw message