You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@isis.apache.org by bu...@apache.org on 2014/10/15 08:19:09 UTC
svn commit: r925802 - in /websites/staging/isis/trunk: cgi-bin/ content/
content/contributors/release-process.html
content/contributors/verifying-releases-script.html
content/contributors/verifying-releases.html
Author: buildbot
Date: Wed Oct 15 06:19:07 2014
New Revision: 925802
Log:
Staging update by buildbot for isis
Modified:
websites/staging/isis/trunk/cgi-bin/ (props changed)
websites/staging/isis/trunk/content/ (props changed)
websites/staging/isis/trunk/content/contributors/release-process.html
websites/staging/isis/trunk/content/contributors/verifying-releases-script.html
websites/staging/isis/trunk/content/contributors/verifying-releases.html
Propchange: websites/staging/isis/trunk/cgi-bin/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Oct 15 06:19:07 2014
@@ -1 +1 @@
-1631944
+1631945
Propchange: websites/staging/isis/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Oct 15 06:19:07 2014
@@ -1 +1 @@
-1631944
+1631945
Modified: websites/staging/isis/trunk/content/contributors/release-process.html
==============================================================================
--- websites/staging/isis/trunk/content/contributors/release-process.html (original)
+++ websites/staging/isis/trunk/content/contributors/release-process.html Wed Oct 15 06:19:07 2014
@@ -1040,7 +1040,7 @@ git fetch
<p>Use the following subject:</p>
<pre>
-[VOTE] Apache Isis Core release 1.7.0 and related components
+[VOTE] Apache Isis Core release 1.7.0 RC1 and related components
</pre>
<p>And use the following body:</p>
@@ -1052,18 +1052,18 @@ I've cut a release for Apache Isis Core
* SimpleApp Archetype 1.7.0
* TodoApp Archetype 1.7.0
-The artifacts have been uploaded to staging repository on repository.apache.org:
+The source code artifacts have been uploaded to staging repositories on repository.apache.org:
-* https://repository.apache.org/service/local/repositories/orgapacheisis-10xx/content/org/apache/isis/core/isis/1.7.0/isis-1.7.0-source-release.zip
-* https://repository.apache.org/service/local/repositories/orgapacheisis-10xx/content/org/apache/isis/viewer/isis-viewer-wicket/1.7.0/isis-viewer-wicket-1.7.0-source-release.zip
-* https://repository.apache.org/service/local/repositories/orgapacheisis-10xx/content/org/apache/isis/archetype/simpleapp-archetype/1.7.0/simpleapp-archetype-1.7.0-source-release.zip
-* https://repository.apache.org/service/local/repositories/orgapacheisis-10xx/content/org/apache/isis/archetype/todoapp-archetype/1.7.0/todoapp-archetype-1.7.0-source-release.zip
+* http://repository.apache.org/content/repositories/orgapacheisis-10xx/org/apache/isis/core/isis/1.7.0/isis-1.7.0-source-release.zip
+* http://repository.apache.org/content/repositories/orgapacheisis-10xx/org/apache/isis/viewer/isis-viewer-wicket/1.7.0/isis-viewer-wicket-1.7.0-source-release.zip
+* http://repository.apache.org/content/repositories/orgapacheisis-10xx/org/apache/isis/archetype/simpleapp-archetype/1.7.0/simpleapp-archetype-1.7.0-source-release.zip
+* http://repository.apache.org/content/repositories/orgapacheisis-10xx/org/apache/isis/archetype/todoapp-archetype/1.7.0/todoapp-archetype-1.7.0-source-release.zip
For each zip there is a corresponding signature file (append .asc to the zip's url).
In the source code repo the code has been tagged as isis-1.7.0-RC1.
-Our website contains some suggestions of how to verify the release, see http://isis.apache.org/contributors/verifying-releases.html. There is also a script you can use, http://isis.apache.org/contributors/verifying-releases-script.html.
+Alternatively, you can add the above staging repositories to your local `~/.m2/settings.xml` file and use directly. Our website describes how to do this, and other suggestions on how to verify the release, at http://isis.apache.org/contributors/verifying-releases.html. There is also a script you can use, http://isis.apache.org/contributors/verifying-releases-script.html.
Please verify the release and cast your vote. The vote will be open for a minimum of 72 hours.
@@ -1072,9 +1072,9 @@ Please verify the release and cast your
[ ] -1
</pre>
-<p>The value <code>orgapacheisis-10xx</code> is the repository id provided by Nexus earlier.</p>
+<p>The value <code>orgapacheisis-10xx</code> is the repository id provided by Nexus earlier; update the email text as required before sending.</p>
-<p>The procedure for other committers to verify the release can be found <a href="verifying-releases.html">here</a>.</p>
+<p>Note that the email also references the procedure for other committers to <a href="verifying-releases.html">verify the release</a>.</p>
<h2>After the vote</h2>
Modified: websites/staging/isis/trunk/content/contributors/verifying-releases-script.html
==============================================================================
--- websites/staging/isis/trunk/content/contributors/verifying-releases-script.html (original)
+++ websites/staging/isis/trunk/content/contributors/verifying-releases-script.html Wed Oct 15 06:19:07 2014
@@ -423,7 +423,9 @@
</h1>
</div>
-<p>To save some time in verifying an Isis release we've assembled a script to automate the process. The script is tested on Mac OSX and should work on Linux too. Windows users can use Cygwin. It's <strong>recommended</strong> that you start this process in an empty directory:</p>
+<p>To save some time in verifying an Isis release we've assembled a script to automate the process. The script is tested on Mac OSX and Linux. Windows users can use Cygwin or gpgWin (the latter is bundled with <a href="http://windows.github.com">Github for Windows</a>).</p>
+
+<p>It's <strong>recommended</strong> that you start this process in an empty directory:</p>
<pre><code>mkdir ~/verify-isis-release
cd ~/verify-isis-release
@@ -431,7 +433,7 @@ cd ~/verify-isis-release
<h2>Copy the script to your local machine</h2>
-<p>The script could be enhanced in many ways, feel free to do so! Copy (or <a href="resources/verify-isis-release.sh">download</a> the <code>verify-isis-release.sh</code> script below:</p>
+<p>The script could be enhanced in many ways, feel free to do so! Copy (or <a href="resources/verify-isis-release.sh">download</a>) the <code>verify-isis-release.sh</code> script below:</p>
<pre><code>#!/bin/bash
# Instructions:
Modified: websites/staging/isis/trunk/content/contributors/verifying-releases.html
==============================================================================
--- websites/staging/isis/trunk/content/contributors/verifying-releases.html (original)
+++ websites/staging/isis/trunk/content/contributors/verifying-releases.html Wed Oct 15 06:19:07 2014
@@ -423,7 +423,7 @@
</h1>
</div>
-<p>Whenever a committer announces a vote on a release on the <a href="../support.html">dev mailing list</a>, it is the responsibility of the project's PMC to cast their vote on the release. Any other ASF member may also vote.</p>
+<p>Whenever a committer announces a vote on a release on the <a href="../support.html">dev mailing list</a>, it is the responsibility of the project's PMC to cast their vote on the release. Anyone else can also vote, but only members of the Apache Isis PMC's vote are binding.</p>
<p>This page provides some guidance on what a voter is expected to verify before casting their vote. </p>
@@ -435,7 +435,7 @@
<li>all dependencies are appropriately licensed; see the <code>DEPENDENCIES</code> file which is automatically generated from the POMs plus the supplemental-models.xml file</li>
</ul>
-<p>Note that the binaries are <em>not</em> an ASF release, they merely exist on the Maven central repo as a convenience.</p>
+<p>Note that the binaries are <em>not</em> an ASF release, they merely exist on the Maven central repo as a convenience. That said, you might also want to verify the release by pulling the binaries from the Maven staging repository. Details of how to do this are also documented below.</p>
<h2>Prerequisites</h2>
@@ -456,9 +456,8 @@ gpg --import /tmp/KEYS
<p>Download both the ZIP and .ASC files from the location specified in the voting email. To verify that the signature is correct, use:</p>
-<pre>
-gpg --verify isis-x.y.z.zip.asc isis-x.y.z.zip
-</pre>
+<pre><code>gpg --verify isis-x.y.z.zip.asc isis-x.y.z.zip
+</code></pre>
<h2>Building the source release artifacts</h2>
@@ -466,45 +465,73 @@ gpg --verify isis-x.y.z.zip.asc isis-x.y
<p>First, delete all Isis artifacts from your local Maven repo:</p>
-<pre>
-rm -rf ~/.m2/repository/org/apache/isis
-</pre>
+<pre><code>rm -rf ~/.m2/repository/org/apache/isis
+</code></pre>
<p>The build process depends on whether the artifact is of Isis core or of one of its components.</p>
-<h3>Isis Core</h3>
+<h4>Isis Core</h4>
<p>To build Isis core, first download any dependencies:</p>
-<pre>
-mvn dependency:go-offline
-</pre>
+<pre><code>mvn dependency:go-offline
+</code></pre>
<p>Check that no Isis artifacts have yet been downloaded, ie there is no <code>~/.m2/org/repository/org/apache/isis</code> directory. If there are, it could indicate that the release being verified incorrectly references previous versions of Isis core.</p>
<p>Assuming all is ok, build using the <code>-o</code> offline flag:</p>
-<pre>
-mvn clean install -o
-</pre>
+<pre><code>mvn clean install -o
+</code></pre>
<p>Confirm that the versions of the Isis artifacts now cached in your local repository are correct.</p>
-<h3>Isis Component</h3>
+<h4>Isis Component</h4>
<p>To build an Isis component, build without the offline flag; Maven should pull down the component's dependencies from the Maven central repo:</p>
-<pre>
-mvn clean install
-</pre>
+<pre><code>mvn clean install
+</code></pre>
<p>Confirm that the versions of the Isis artifacts now cached in your local repository are correct (both those pulled down from Maven central repo, as well as those of the component built locally).</p>
<p>The above steps are the bare minimum you should perform before casting a vote. Ideally, you should also run an Isis application (eg one of the examples) against the new code (either against a new version of core, or configured to use the new version of the component).</p>
-<h2>Verifying the binary release artifacts</h2>
+<h2>Verifying the binary release artifacts (using the Maven staging repository)</h2>
+
+<p>If you wish, you can verify the binary releases by configuring your local Maven install to point to the Maven Maven staging repository (or repositories) and then using them, eg to run the <a href="../intro/getting-started/simpleapp-archetype.html">simpleapp archetype</a> and running the resultant app.</p>
+
+<p>Configuring your local Maven install amounts to updating the <code>~/.m2/settings.xml</code> file:</p>
+
+<pre><code><profiles>
+ <profile>
+ <id>verify-isis</id>
+ <repositories>
+ <repository>
+ <id>isis-core-staging</id>
+ <name>Isis Core Staging</name>
+ <releases>
+ <enabled>true</enabled>
+ <updatePolicy>always</updatePolicy>
+ <checksumPolicy>warn</checksumPolicy>
+ </releases>
+ <url>http://repository.apache.org/content/repositories/orgapacheisis-10xx</url>
+ <layout>default</layout>
+ </repository>
+ ...
+ </repositories>
+ <profile>
+ ...
+</profiles>
+<activeProfiles>
+ <activeProfile>verify-isis</activeProfile>
+ ...
+</activeProfiles>
+</code></pre>
+
+<p>where the repository URL is as provided in the VOTE email. If there is more than one repository (as is sometimes the case if multiple components have been released), then repeat the <repository> section for each.</p>
-<p>Optionally, you can verify the binary releases (in the Maven staging repository). For this it is necessary to download each artifact from Nexus and its corresponding .ASC file. Since there are many such artifacts, just verify one or two at random.</p>
+<p>Once the vote has completed, the staging repositories will be removed and so you should deactive the profile (comment out the <code><activeProfile></code> element). If you forget to deactive the profile, there should be no adverse effects; Maven will just spend unnecessary cycles attempting to hit a non-existent repo.</p>
<h2>Using the Creadur Tools</h2>