You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@aries.apache.org by bu...@apache.org on 2012/05/18 19:44:41 UTC

svn commit: r818205 - in /websites/staging/aries/trunk/content: ./ development/verifyingrelease.html

Author: buildbot
Date: Fri May 18 17:44:41 2012
New Revision: 818205

Log:
Staging update by buildbot for aries

Modified:
    websites/staging/aries/trunk/content/   (props changed)
    websites/staging/aries/trunk/content/development/verifyingrelease.html

Propchange: websites/staging/aries/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri May 18 17:44:41 2012
@@ -1 +1 @@
-1340180
+1340186

Modified: websites/staging/aries/trunk/content/development/verifyingrelease.html
==============================================================================
--- websites/staging/aries/trunk/content/development/verifyingrelease.html (original)
+++ websites/staging/aries/trunk/content/development/verifyingrelease.html Fri May 18 17:44:41 2012
@@ -263,9 +263,10 @@
           </td>
           <td height="100%" width="100%">
             <!-- Content -->
-            <div class="wiki-content"><p>This page provides some help for anyone who wants to verify release candidate artifacts so they feel they can genuinely vote on the related vote thread on the dev list. It is not intended to be exhaustive instructions. It's a list of things people have generally found to be useful to do when checking the artifacts.</p>
+            <div class="wiki-content"><h1 id="verifying-release-artifacts">Verifying Release Artifacts</h1>
+<p>This page provides some help for anyone who wants to verify release candidate artifacts so they feel they can genuinely vote on the related vote thread on the dev list. It is not intended to be exhaustive instructions. It's a list of things people have generally found to be useful to do when checking the artifacts.</p>
 <p>It is essential that the signatures and hashsums are good. Please do read <a href="http://httpd.apache.org/dev/verification.html">Verifying Apache HTTP Server Releases</a> for information on why you should verify releases.. </p>
-<h1 id="have-i-got-the-keys">Have I got the KEYS?</h1>
+<h2 id="have-i-got-the-keys">Have I got the KEYS?</h2>
 <p>To verify Aries release artifacts you need the public keys for the Aries committers.
 The master KEYS file is in Subversion. The easiest way of getting it from the command line is to non-recursively check-out the files in the top level of the Aries location using:</p>
 <div class="codehilite"><pre><span class="n">svn</span> <span class="n">checkout</span> <span class="o">-</span><span class="n">N</span> <span class="n">https:</span><span class="sr">//s</span><span class="n">vn</span><span class="o">.</span><span class="n">apache</span><span class="o">.</span><span class="n">org</span><span class="sr">/repos/</span><span class="n">asf</span><span class="o">/</span><span class="n">aries</span>
@@ -277,7 +278,7 @@ The master KEYS file is in Subversion. T
 </pre></div>
 
 
-<h1 id="download-artifacts">Download artifacts</h1>
+<h2 id="download-artifacts">Download artifacts</h2>
 <p>For each 'useful' file there are several others created to help you determine whether it's genuine. The PGP signature .asc file shows who created the 'useful' file. Then there are checksum files (.md5 and .sha1) for both the 'useful' file and the .asc file. To download the content for the repository you're verifying try this:</p>
 <div class="codehilite"><pre><span class="n">wget</span> <span class="o">-</span><span class="n">e</span> <span class="n">robots</span><span class="o">=</span><span class="n">off</span> <span class="o">--</span><span class="nb">no</span><span class="o">-</span><span class="n">check</span><span class="o">-</span><span class="n">certificate</span> <span class="o">-</span><span class="n">np</span> <span class="o">-</span><span class="n">r</span> <span class="o">-</span><span class="n">nH</span> <span class="n">https:</span><span class="sr">//</span><span class="n">repository</span><span class="o">.</span><span class="n">apache</span><span class="o">.</span><span class="n">org</span><span class="sr">/content/</span><span class="n">repositories</span><span class="sr">/orgapachearies-xxx/o</span><span class="n">rg</span><span class="sr">/apache/</span><span class="n">aries</span><span class="o">/</span>
 </pre></div>
@@ -285,7 +286,7 @@ The master KEYS file is in Subversion. T
 
 <p>where xxx is the number of the repository you're verifying.</p>
 <p>wget will download the files into a directory called content. The following use of the 'find' command assumes the downloads are in the 'content' directory.</p>
-<h1 id="verify-the-artifacts">Verify the artifacts</h1>
+<h2 id="verify-the-artifacts">Verify the artifacts</h2>
 <p>Ensure the checksums are right for the released files. Copy/paste this into the command line:</p>
 <div class="codehilite"><pre><span class="k">for</span> <span class="n">i</span> <span class="n">in</span> <span class="sb">`find content -type f | egrep -v &#39;.md5$|.sha1$|index.html|maven-metadata.xml&#39;`</span>
 <span class="k">do</span>
@@ -325,7 +326,7 @@ The master KEYS file is in Subversion. T
 
 
 <p>You shouldn't get any errors.</p>
-<h1 id="build-the-code">Build the code</h1>
+<h2 id="build-the-code">Build the code</h2>
 <p>It's a good idea to check the source release zip builds. Unzip it first:</p>
 <div class="codehilite"><pre><span class="n">find</span> <span class="o">.</span> <span class="o">-</span><span class="n">name</span> <span class="o">*-</span><span class="n">source</span><span class="o">-</span><span class="n">release</span><span class="o">.</span><span class="n">zip</span> <span class="o">|</span><span class="n">xargs</span> <span class="o">-</span><span class="n">n</span> <span class="mi">1</span> <span class="n">unzip</span>
 </pre></div>
@@ -336,7 +337,7 @@ The master KEYS file is in Subversion. T
 </pre></div>
 
 
-<h1 id="rat-check">RAT check</h1>
+<h2 id="rat-check">RAT check</h2>
 <p>It's also a good idea to run the <a href="http://incubator.apache.org/rat/">Apache RAT (Release Audit Tool)</a>. The Aries POMs are set up so you can do:</p>
 <div class="codehilite"><pre><span class="n">mvn</span> <span class="o">-</span><span class="n">fn</span> <span class="o">-</span><span class="n">Prat</span>
 </pre></div>