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/06/26 22:52:10 UTC
svn commit: r823372 - in /websites/staging/aries/trunk/content: ./
development/devlistvote.txt development/releasingaries.html
development/verifyingrelease.html
Author: buildbot
Date: Tue Jun 26 20:52:09 2012
New Revision: 823372
Log:
Staging update by buildbot for aries
Modified:
websites/staging/aries/trunk/content/ (props changed)
websites/staging/aries/trunk/content/development/devlistvote.txt
websites/staging/aries/trunk/content/development/releasingaries.html
websites/staging/aries/trunk/content/development/verifyingrelease.html
Propchange: websites/staging/aries/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Jun 26 20:52:09 2012
@@ -1 +1 @@
-1352875
+1354221
Modified: websites/staging/aries/trunk/content/development/devlistvote.txt
==============================================================================
--- websites/staging/aries/trunk/content/development/devlistvote.txt (original)
+++ websites/staging/aries/trunk/content/development/devlistvote.txt Tue Jun 26 20:52:09 2012
@@ -1,56 +1,22 @@
-I've staged a release candidate for Aries 0.2-incubating. The
-following Aries top level modules are staged and tagged in
-https://svn.apache.org/repos/asf/incubator/aries/tags/
+I've staged a release candidate for the Aries 1.0.0 test support module. The
+module is staged and tagged in
+https://svn.apache.org/repos/asf/aries/tags/org.apache.aries.testsupport.unit-1.0.0/.
-The artifacts are in two staged repos. Links to the *.zip files for each module are provided below. The source should be built in the order given below because there are dependencies between some of the modules.
+Instructions for doing a verifying the release are at http://aries.apache.org/development/verifyingrelease.html. Alternately, cut and paste the following to run a full check:
-Modules staged at
-https://repository.apache.org/content/repositories/orgapachearies-113/
-are:
+wget --no-check-certificate https://svn.apache.org/repos/asf/aries/scripts/verify_staged_release.sh
+chmod a+x verify_staged_release.sh
+./verify_staged_release.sh 256 mytempdirectory &> verifyresults.txt
+grep FAIL verifyresults.txt
-parent
-https://repository.apache.org/content/repositories/orgapachearies-113/org/apache/aries/parent/0.2-incubating/parent-0.2-incubating-source-release.zip
-eba-maven-plugin
-https://repository.apache.org/content/repositories/orgapachearies-113/org/apache/aries/eba-maven-plugin/0.2-incubating/eba-maven-plugin-0.2-incubating-source-release.zip
+Artifacts are in one staged repo,
+https://repository.apache.org/content/repositories/orgapachearies-256/.
+Links to the *.zip files for each module are provided below.
-testsupport
-https://repository.apache.org/content/repositories/orgapachearies-113/org/apache/aries/testsupport/testsupport/0.2-incubating/testsupport-0.2-incubating-source-release.zip
+The only module staged is the parent module:
-org.apache.aries.util
-https://repository.apache.org/content/repositories/orgapachearies-113/org/apache/aries/org.apache.aries.util/0.2-incubating/org.apache.aries.util-0.2-incubating-source-release.zip
-
-blueprint
-https://repository.apache.org/content/repositories/orgapachearies-113/org/apache/aries/blueprint/blueprint/0.2-incubating/blueprint-0.2-incubating-source-release.zip
-
-web
-https://repository.apache.org/content/repositories/orgapachearies-113/org/apache/aries/web/web/0.2-incubating/web-0.2-incubating-source-release.zip
-
-jmx
-https://repository.apache.org/content/repositories/orgapachearies-113/org/apache/aries/jmx/jmx/0.2-incubating/jmx-0.2-incubating-source-release.zip
-
-
-Modules staged at
-https://repository.apache.org/content/repositories/orgapachearies-129/
-are:
-
-quiesce
-https://repository.apache.org/content/repositories/orgapachearies-129/org/apache/aries/quiesce/quiesce/0.2-incubating/quiesce-0.2-incubating-source-release.zip
-
-jndi
-https://repository.apache.org/content/repositories/orgapachearies-129/org/apache/aries/jndi/jndi/0.2-incubating/jndi-0.2-incubating-source-release.zip
-
-transaction
-https://repository.apache.org/content/repositories/orgapachearies-129/org/apache/aries/transaction/transaction/0.2-incubating/transaction-0.2-incubating-source-release.zip
-
-jpa
-https://repository.apache.org/content/repositories/orgapachearies-129/org/apache/aries/jpa/jpa/0.2-incubating/jpa-0.2-incubating-source-release.zip
-
-application
-https://repository.apache.org/content/repositories/orgapachearies-129/org/apache/aries/application/application/0.2-incubating/application-0.2-incubating-source-release.zip
-
-samples
-https://repository.apache.org/content/repositories/orgapachearies-129/org/apache/aries/samples/samples/0.2-incubating/samples-0.2-incubating-source-release.zip
+https://repository.apache.org/content/repositories/orgapachearies-256/org/apache/aries/testsupport/org.apache.aries.testsupport.unit/1.0.0/org.apache.aries.testsupport.unit-1.0.0-source-release.zip
The RAT and IANAL build checks passed. Note that, although RAT is configured to ignore *.MF and other files that do not require the ASF licence, theses files are still reported incorrectly as RAT failures.
@@ -59,3 +25,4 @@ The vote will be open for 72 hours.
[ ] +1
[ ] 0
[ ] -1
+
Modified: websites/staging/aries/trunk/content/development/releasingaries.html
==============================================================================
--- websites/staging/aries/trunk/content/development/releasingaries.html (original)
+++ websites/staging/aries/trunk/content/development/releasingaries.html Tue Jun 26 20:52:09 2012
@@ -382,7 +382,7 @@ instructions in the file) and checkin</p
<h3 id="setting-up-your-environment">Setting up your environment</h3>
<p>Follow the general instructions linked to above. </p>
<p><a name="ReleasingAries-Creatingabranchtoreleasefrom"></a></p>
-<h3 id="creating-a-branch-to-release-from">Creating a branch to release from</h3>
+<h3 id="creating-a-branch-to-release-from-if-needed">Creating a branch to release from (if needed)</h3>
<p>It is strongly recomended that releases are made from trunk and NEVER from a branch. But, if you have to release from a branch this is what
you will need to do:</p>
<div class="codehilite"><pre><span class="n">svn</span> <span class="n">copy</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="sr">/aries/</span><span class="n">trunk</span> <span class="o">\</span>
@@ -492,7 +492,7 @@ trunk.</p>
<p>For each bundle that needs to be release perform the following commands:</p>
<div class="codehilite"><pre><span class="n">Check</span> <span class="n">that</span> <span class="n">there</span> <span class="n">are</span> <span class="nb">no</span> <span class="n">depndencies</span> <span class="n">on</span> <span class="o">-</span><span class="n">SNAPSHOT</span> <span class="n">versions</span><span class="o">.</span>
<span class="n">Ensure</span> <span class="n">that</span> <span class="n">everything</span> <span class="n">is</span> <span class="n">committed</span> <span class="n">in</span> <span class="n">SVN</span>
-<span class="n">mvn</span> <span class="n">release:prepare</span> <span class="o">-</span><span class="n">Papache</span><span class="o">-</span><span class="n">release</span> <span class="o">-</span><span class="n">DpreparationGoals</span><span class="o">=</span><span class="s">"clean install"</span>
+<span class="n">mvn</span> <span class="n">release:prepare</span> <span class="o">-</span><span class="n">Papache</span><span class="o">-</span><span class="n">release</span> <span class="o">-</span><span class="n">DpreparationGoals</span><span class="o">=</span><span class="s">"clean install"</span> <span class="o">-</span><span class="n">DwaitBeforeTagging</span><span class="o">=</span><span class="s">"10"</span> <span class="o">-</span><span class="n">DscmCommentPrefix</span><span class="o">=</span><span class="s">"[ARIES-xxx][maven-release-plugin]"</span>
<span class="n">mvn</span> <span class="n">release:perform</span> <span class="o">-</span><span class="n">Papache</span><span class="o">-</span><span class="n">release</span>
</pre></div>
@@ -505,14 +505,14 @@ trunk.</p>
<li>What is the release version for "Aries :: Top Parent POM"? (org.apache.aries:parent) 0.5: : <br />
</li>
<li>What is SCM release tag or label for "Aries :: Top Parent POM"? (org.apache.aries:parent) parent-0.5: :</li>
-<li>What is the new development version for "Aries :: Top Parent POM"? (org.apache.aries:parent) 0.6-SNAPSHOT: : 0.5</li>
+<li>What is the new development version for "Aries :: Top Parent POM"? (org.apache.aries:parent) 0.6-SNAPSHOT: : 0.5.1</li>
</ol>
-<p>i.e. take the default for the first two questions, and set the new development version to be the same as the one you are releasing! This is because you don't know whether the next version released from the trunk will have a major, minor or micro version number change - you won't know until those changes are made! - so leave it for the person making those changes to make the decision and move to <em>module</em>-<em>new version</em>-SNAPSHOT.</p>
+<p>i.e. take the defaults for the last two questions, but change the release version if required. You don't know whether the next version released from the trunk will have a major, minor or micro version number change - you won't know until those changes are made! - but you have to make a guess. The person doing the next release can make the decision and move to <em>module</em>-<em>new version</em>-SNAPSHOT.
+ * Note 3: Since the release plugin makes changes in SCM, use a JIRA for the release (ARIES-XXX here) in the commit comment to make it easier to see what's changed
+ * Note 4: The task will appear to hang at the end. It's waiting ten seconds to do the tagging, to ensure everything works in Europe, where svn is mirrored from a US master
+<em> Note 3: mvn release:clean will do </em>most* of the cleaning up in the event of failures.
+ * Note 4: If on mvn release:prepare you get an error from SVN similar to https://svn.apache.org/repos/asf/!svn/bc/1182408/aries/tags/parent-0.5/default-parent/java5-parent/org.apache.aries.bundle.i.am.releasing does not exist then it's because there's no scm element in the pom.xml for the module you're releasing.</p>
</li>
-<li>
-<p>Note 3: mvn release:clean will do <em>most</em> of the cleaning up in the event of failures.</p>
-</li>
-<li>Note 4: If on mvn release:prepare you get an error from SVN similar to https://svn.apache.org/repos/asf/!svn/bc/1182408/aries/tags/parent-0.5/default-parent/java5-parent/org.apache.aries.bundle.i.am.releasing does not exist then it's because there's no scm element in the pom.xml for the module you're releasing.</li>
</ul>
<p>This will put release artifacts into an Apache <a href="https://repository.apache.org/index.html#view-repositories;staging.html">staging repository </a>. You will need to log in to see it.
If nothing appears in a staging repo you should stop here and work out why.
@@ -520,25 +520,6 @@ If you have made a mistake it's quite ea
commands make and commit changes to the project's pom.xml files and they
create a tag in SVN. To revert the changes you will need to revert the
pom.xml files and delete the tag from svn.</p>
-<p>If you are in Europe the mvn release:prepare command almost always fails at
-the last step, with a message like:</p>
-<div class="codehilite"><pre><span class="k">[ERROR]</span>
- <span class="err">BUILD</span> <span class="err">FAILURE</span>
-<span class="k">[INFO]</span>
- <span class="err">------------------------------------------------------------------------</span>
-<span class="k">[INFO]</span>
- <span class="err">Unable</span> <span class="err">to</span> <span class="err">tag</span> <span class="err">SCM</span>
-<span class="err">Provider</span> <span class="err">message:</span>
-<span class="err">The</span> <span class="err">svn</span> <span class="err">tag</span> <span class="err">command</span> <span class="err">failed.</span>
-<span class="err">Command</span> <span class="err">output:</span>
-<span class="err">svn:</span> <span class="err">No</span> <span class="err">such</span> <span class="err">revision</span> <span class="err">936951</span>
-</pre></div>
-
-
-<p>This is due to the SVN mirroring in place between Europe and the master in
-the US. When you make a commit, it isn't immediately available in Europe to
-svn up to. Just wait 10 secs and repeat the mvn release:prepare command for
-it to restart where it left off.</p>
<p><a name="ReleasingAries-Closingthestagingrepository"></a></p>
<h5 id="closing-the-staging-repository">Closing the staging repository</h5>
<p>After checking that the staging repository contains the artifacts that you
@@ -547,7 +528,7 @@ so that people can check the release.</p
<p><a name="ReleasingAries-Runningthevote(s)"></a></p>
<h3 id="running-the-vote">Running the vote.</h3>
<p>At this
-point you should write two notes to the dev@aries.apache.org mailing list.</p>
+point you should write two notes to the dev@aries.apache.org mailing list. You may wish to ensure they have slightly different subjects, since googlemail seems to ignore anything in brackets when threading. </p>
<ul>
<li>Subject [VOTE]
Apache Aries release candidate 0N</li>
@@ -584,9 +565,12 @@ archived here /www/archive.apache.org/di
<p>Then, put new release artifacts in the distribution directory. This is best done using a script, the script can be generated uing
the perl script <a href="http://svn.apache.org/repos/asf/aries/scripts/download_release_artifacts.pl">download_release_artifacts.pl</a>. </p>
<p>Next, update the Aries Downloads pages to refer to the new artifacts.</p>
+<h3 id="updating-dependencies">Updating dependencies</h3>
+<p>Once the release is promoted, change all the bundles which depend on the SNAPSHOT to depend on the released version. Deployed snapshots get regularly cleaned from the repositories if there's a released version available, so building against them isn't reliable. </p>
+<p>Don't move bundles which depend on earlier releases to depend on the new release, or they won't be able to run in an environment with the older bundles. </p>
<h3 id="tidying-up-tasks">Tidying up tasks</h3>
<ul>
-<li>Get the compliance tests run</li>
+<li>Get the <a href="http://aries.apache.org/development/compliancetesting.html">compliance tests</a> run</li>
<li>Release notes</li>
<li>Release the component in JIRA (manage components), check the JIRA release notes.</li>
</ul>
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 Tue Jun 26 20:52:09 2012
@@ -269,6 +269,14 @@
<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>
+<p>These instructions have been rolled up into a script, which you can run instead. Cut and paste the following:</p>
+<div class="codehilite"><pre><span class="n">wget</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="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="sr">/aries/sc</span><span class="n">ripts</span><span class="o">/</span><span class="n">verify_staged_release</span><span class="o">.</span><span class="n">sh</span>
+<span class="nb">chmod</span> <span class="n">a</span><span class="o">+</span><span class="n">x</span> <span class="n">verify_staged_release</span><span class="o">.</span><span class="n">sh</span>
+<span class="o">./</span><span class="n">verify_staged_release</span><span class="o">.</span><span class="n">sh</span> <span class="p">[</span><span class="n">RELEASE</span><span class="o">-</span><span class="n">NUM</span><span class="p">]</span> <span class="n">mytempdirectory</span> <span class="o">&></span> <span class="n">verifyresults</span><span class="o">.</span><span class="n">txt</span>
+<span class="nb">grep</span> <span class="n">FAIL</span> <span class="n">verifyresults</span><span class="o">.</span><span class="n">txt</span>
+</pre></div>
+
+
<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>
@@ -305,6 +313,7 @@ The master KEYS file is in Subversion. T
</pre></div>
+<p>(On the Mac, use <code>md5 -q</code> instead of <code>md5sum</code> and the cut.)</p>
<p>Do something similar for sha1:</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 '.md5$|.sha1$|index.html|maven-metadata.xml'`</span>
<span class="k">do</span>
@@ -320,6 +329,7 @@ The master KEYS file is in Subversion. T
</pre></div>
+<p>(On the Mac, use <code>openssl sha1</code> instead of <code>sha1sum</code>.)</p>
<p>Ensure the PGP signature files are good. See the <a href="http://httpd.apache.org/dev/verification.html#Validating">Validating section of Verifying Apache HTTP Server Releases</a> for background on validating the authenticity of a key.</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 '.asc$'`</span>
<span class="k">do</span>
@@ -346,7 +356,9 @@ The master KEYS file is in Subversion. T
</pre></div>
-<p>Note: currently RAT fails due to the generated DEPENDENCIES file not containing a license. It's safe to ignore this as the file is generated. So in order to ensure RAT checks all subdirectories, use the -fn.</p></div>
+<p>Note: currently RAT fails due to the generated DEPENDENCIES file not containing a license. It's safe to ignore this as the file is generated. So in order to ensure RAT checks all subdirectories, use the -fn. Then check any failures with</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">rat</span> <span class="o">|</span> <span class="n">xargs</span> <span class="nb">grep</span> <span class="o">\!\</span><span class="p">?</span><span class="o">\</span><span class="p">?</span>
+</pre></div></div>
<!-- Content -->
</td>
</tr>