sis-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r874574 - in /websites/staging/sis/trunk/content: ./ release-management.html
Date Wed, 14 Aug 2013 10:37:36 GMT
Author: buildbot
Date: Wed Aug 14 10:37:36 2013
New Revision: 874574

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 Aug 14 10:37:36 2013
@@ -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 Wed Aug 14 10:37:36 2013
@@ -103,6 +103,7 @@ The intended audiences are SIS release m
 <li><a href="#tag">Create tag</a></li>
 <li><a href="#maven-deploy">Deploy Maven artifacts</a><ul>
 <li><a href="#nexus-close">Verify and close the Nexus release artifacts</a></li>
+<li><a href="#nexus-text">Test the Nexus release artifacts</a></li>
 <li><a href="#stage">Stage the source, binary and javadoc artifacts</a><ul>
@@ -320,8 +321,12 @@ mvn org.apache.sis.core:sis-build-helper
-<p>If the above succeeded, deploy:</p>
-<div class="codehilite"><pre>mvn deploy --activate-profiles apache-release
+<p>If the above succeeded, deploy. We temporarily delete the Maven site descriptors
+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
+svn revert . --recursive
@@ -343,8 +348,6 @@ so try to see at least one code snippet.
 <li>Delete all <code>org/apache/sis/parent/$NEW_VERSION/parent-$*</code>
files on the Nexus repository.
     They should not be there - source release will be deployed on an other repository later.</li>
-<li>Delete all <code>org/apache/sis/*/$NEW_VERSION/*-$NEW_VERSION-site.xml*</code>
-    There is no apparent reason for deploying Maven web site descriptors.</li>
 <p>Close the Nexus staging repository:</p>
@@ -356,6 +359,23 @@ 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
+<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>
+<p>Clear the local Maven repository in order to force downloads from the Nexus repository,
then test.
+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
 <h1 id="stage">Stage the source, binary and javadoc artifacts</h1>
 <p>Generate the Javadoc. While not mandatory, we suggest to use JDK 7 or above for
getting the new look and feel,
 getting the Javadoc enhancements expected in future JDK releases (more dynamic pages),
@@ -406,7 +426,7 @@ mv sis-<span class="nv">$NEW_VERSION</sp
 <span class="nb">cd </span>apache-sis-<span class="nv">$NEW_VERSION</span>
 cp <span class="nv">$TAG_DIR</span>/LICENSE .
 cp <span class="nv">$TAG_DIR</span>/NOTICE .
-mv <span class="nv">$TAG</span>/target/bundles/sis-<span class="nv">$NEW_VERSION</span>.pack.gz
+mv <span class="nv">$TAG_DIR</span>/target/bundles/apache-sis-<span class="nv">$NEW_VERSION</span>.pack.gz
 <span class="nb">cd</span> ..
 zip -9 -r apache-sis-<span class="nv">$NEW_VERSION</span> apache-sis-<span
 rm -r apache-sis-<span class="nv">$NEW_VERSION</span>
@@ -428,6 +448,13 @@ gpg --print-md MD5    apache-sis-<span c
+<p>Verify checksums and signatures:</p>
+<div class="codehilite"><pre>find . -name <span class="s2">&quot;*.md5&quot;</span>
-exec shasum --check <span class="s1">&#39;{}&#39;</span> <span class="se">\;</span>
+find . -name <span class="s2">&quot;*.sha&quot;</span> -exec shasum --check
<span class="s1">&#39;{}&#39;</span> <span class="se">\;</span>
+find . -name <span class="s2">&quot;*.asc&quot;</span> -exec gpg --verify
<span class="s1">&#39;{}&#39;</span> <span class="se">\;</span>
 <div class="codehilite"><pre>svn add apache-sis-<span class="nv">$NEW_VERSION</span>-*
 <span class="nb">cd</span> ../..
@@ -436,7 +463,7 @@ svn commit --message <span class="s2">&q
 <p>Verify that the files are downloadable from the
+<a href=""></a>
 <h2 id="apidocs">Update online Javadoc</h2>
 <p>Copy the Javadoc to the web site staging directory:</p>
 <div class="codehilite"><pre><span class="nb">cd</span> ../site/content
@@ -462,10 +489,12 @@ svn status | gawk <span class="s1">&#39;
 <li>a -1 vote does not necessarily mean that the vote must be redone, however it is
usually a good idea
     to rollback the release if a -1 vote is received. See <em>Recovering from a vetoed
release</em> below.</li>
 <li>After the vote has been open for at least 72 hours, has at least three +1 PMC votes
and no -1 votes,
-    then post the results to the vote thread:</li>
+    then post the results to the vote thread:<ul>
 <li>Reply to the initial email and prepend to the original subject "[RESULT]"</li>
 <li>Include a list of everyone who voted +1, 0 or -1.</li>
 <h2 id="veto">Recovering from a vetoed release</h2>
 <p>Reply to the initial vote email and prepend to the original subject:</p>
 <div class="codehilite"><pre>[CANCELED]

View raw message