Author: buildbot
Date: Thu Feb 12 15:01:10 2015
New Revision: 939950
Log:
Staging update by buildbot for sis
Modified:
websites/staging/sis/trunk/content/ (props changed)
websites/staging/sis/trunk/content/index.html
websites/staging/sis/trunk/content/release-management.html
Propchange: websites/staging/sis/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Feb 12 15:01:10 2015
@@ -1 +1 @@
-1657940
+1659282
Modified: websites/staging/sis/trunk/content/index.html
==============================================================================
--- websites/staging/sis/trunk/content/index.html (original)
+++ websites/staging/sis/trunk/content/index.html Thu Feb 12 15:01:10 2015
@@ -100,6 +100,7 @@ The version under development is 0.6-SNA
<ul>
<li><a href="downloads.html">Downloads</a> as a <code>zip</code> files, or as
Maven dependencies.</li>
<li>Developer guide (<a href="book/en/developer-guide.html">English</a> | <a
href="book/fr/developer-guide.html">French</a>) â note that this is work in
progress.</li>
+<li><a href="apidocs/index.html">Online Javadoc</a> for API documentation.</li>
<li><a href="command-line.html">Command-line interface</a> for an overview of
a command-line tool.</li>
<li><a href="http://cwiki.apache.org/confluence/display/SIS";>SIS Wiki</a> for
"drawing board" and roadmap.</li>
<li><a href="code-patterns.html">Recommended code patterns</a> for writing
more robust applications.</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 Thu Feb 12
15:01:10 2015
@@ -556,7 +556,7 @@ Promote the staged Nexus artifacts, by r
<p>Check in the source and binary artifacts into distribution svn which will
be pulled by all mirrors within 24 hours.
The <code>dist/dev</code> svn is not mirrored, but the
<code>dist/release</code> is.
From any directory:</p>
-<div class="codehilite"><pre>svn copy
https://dist.apache.org/repos/dist/dev/sis/<span
class="nv">$NEW_VERSION</span>/RC<span class="nv">$RELEASE_CANDIDATE</span>
<span class="se">\</span>
+<div class="codehilite"><pre>svn move
https://dist.apache.org/repos/dist/dev/sis/<span
class="nv">$NEW_VERSION</span>/RC<span class="nv">$RELEASE_CANDIDATE</span>
<span class="se">\</span>
https://dist.apache.org/repos/dist/release/sis/<span
class="nv">$NEW_VERSION</span> <span class="se">\</span>
--message <span class="s2">"Committing SIS Source and Binary Release
Candidate $RELEASE_CANDIDATE for SIS-$NEW_VERSION."</span>
@@ -565,18 +565,6 @@ svn delete https://dist.apache.org/repos
</pre></div>
-<p>Delete the prior version:</p>
-<div class="codehilite"><pre>svn delete
https://dist.apache.org/repos/dist/release/sis/<span
class="nv">$OLD_VERSION</span> <span class="se">\</span>
- --message <span class="s2">"Archive SIS-$OLD_VERSION after release of
SIS-$NEW_VERSION."</span>
-</pre></div>
-
-
-<p>Update the staged web site:</p>
-<ul>
-<li>Make a news announcement on the SIS home page.</li>
-<li>Update the downloads page to add new version using the mirrored URLs.</li>
-<li>Modify the URL for the prior release to the archived URL for the
release.</li>
-</ul>
<p>Update <a href="http://issues.apache.org/jira/browse/SIS";>JIRA</a>:</p>
<ul>
<li>Update the JIRA versions to mark the version as "released".</li>
@@ -606,6 +594,12 @@ svn delete https://dist.apache.org/repos
A template is available <a href="templates/release-announce.txt">here</a>.
The email needs to be sent from an <code>@apache.org</code> email
address.</li>
</ul>
+<p>Delete the prior version:</p>
+<div class="codehilite"><pre>svn delete
https://dist.apache.org/repos/dist/release/sis/<span
class="nv">$OLD_VERSION</span> <span class="se">\</span>
+ --message <span class="s2">"Archive SIS-$OLD_VERSION after release of
SIS-$NEW_VERSION."</span>
+</pre></div>
+
+
<h1 id="next-release">Update trunk for the next development cycle</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>
