You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airavata.apache.org by bu...@apache.org on 2013/07/01 04:45:40 UTC
svn commit: r867968 - in /websites/staging/airavata/trunk/content: ./
development/release-management.html
Author: buildbot
Date: Mon Jul 1 02:45:40 2013
New Revision: 867968
Log:
Staging update by buildbot for airavata
Modified:
websites/staging/airavata/trunk/content/ (props changed)
websites/staging/airavata/trunk/content/development/release-management.html
Propchange: websites/staging/airavata/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Jul 1 02:45:40 2013
@@ -1 +1 @@
-1470259
+1498207
Modified: websites/staging/airavata/trunk/content/development/release-management.html
==============================================================================
--- websites/staging/airavata/trunk/content/development/release-management.html (original)
+++ websites/staging/airavata/trunk/content/development/release-management.html Mon Jul 1 02:45:40 2013
@@ -181,14 +181,13 @@ The popular software used Open Pretty Go
<p>Before performing the following release steps, ensure the <a href="#release-setup">Release Setup</a> steps have been performed.</p>
</li>
<li>
-<p>Ensure the source is ready for release. Verify: <br />
-</p>
+<p>Ensure the source is ready for release. Verify: </p>
<ul>
<li>Cleanup JIRA so the Fix Version in issues resolved since the last release includes this release version correctly.</li>
<li>Ensure all open issues are resolved before proceeding further, close all resolved issues.</li>
<li>Test and make sure the release passes all regression tests.</li>
<li>Update RELEASE_NOTES with all the features added.<ul>
-<li>The release notes can be obtained from JIRA, by clicking the version, and then configuring the release notes to display text format and copying it.</li>
+<li>The release notes can be obtained from JIRA, by clicking the RoadMap, version, and then configuring the release notes to display text format and copying it.</li>
<li>A suggested approach would be to reorganize the release notes as New Features, then Improvements then Tasks and Sub Tasks and finally Bug Fixes.</li>
</ul>
</li>
@@ -200,21 +199,21 @@ The popular software used Open Pretty Go
<li>
<p>Checkout a clean copy of the trunk to release using command line svn.
<em>Do not use Eclipse to do the checkout. The extra dot (.) files created by Eclipse throws off the rat:check processing.</em></p>
-<div class="codehilite"><pre><span class="sb">`svn co https://svn.apache.org/repos/asf/airavata/trunk airavata-trunk`</span>
+<div class="codehilite"><pre>`<span class="n">svn</span> <span class="n">co</span> <span class="n">https</span><span class="p">:</span><span class="o">//</span><span class="n">svn</span><span class="p">.</span><span class="n">apache</span><span class="p">.</span><span class="n">org</span><span class="o">/</span><span class="n">repos</span><span class="o">/</span><span class="n">asf</span><span class="o">/</span><span class="n">airavata</span><span class="o">/</span><span class="n">trunk</span> <span class="n">airavata</span><span class="o">-</span><span class="n">trunk</span>`
</pre></div>
</li>
<li>
<p>Verify the source has the required license headers before trying to release: </p>
-<div class="codehilite"><pre><span class="sb">`mvn -P pedantic verify -DskipTests=true`</span>
+<div class="codehilite"><pre>`<span class="n">mvn</span> <span class="o">-</span><span class="n">P</span> <span class="n">pedantic</span> <span class="n">verify</span> <span class="o">-</span><span class="n">DskipTests</span><span class="p">=</span><span class="n">true</span>`
</pre></div>
</li>
<li>
<p>Do a dry run of the release:prepare step:</p>
-<div class="codehilite"><pre><span class="sb">`mvn -P apache-release release:prepare -DautoVersionSubmodules=true -DdryRun=true`</span>
+<div class="codehilite"><pre>`<span class="n">mvn</span> <span class="o">-</span><span class="n">P</span> <span class="n">apache</span><span class="o">-</span><span class="n">release</span> <span class="n">release</span><span class="p">:</span><span class="n">prepare</span> <span class="o">-</span><span class="n">DautoVersionSubmodules</span><span class="p">=</span><span class="n">true</span> <span class="o">-</span><span class="n">DdryRun</span><span class="p">=</span><span class="n">true</span>`
</pre></div>
@@ -232,23 +231,21 @@ The popular software used Open Pretty Go
<p>Verify that the release process completed as expected</p>
<ul>
<li>The release plugin will create pom.xml.tag files which contain the changes that would have been committed to SVN. The only differences between pom.xml.tag and it's corresponding pom.xml file should be the version number.</li>
-<li>If other formatting changes have been made you should review the changes and then commit them <code>svn commit -m "fixing formatting for release"</code><br />
-</li>
+<li>If other formatting changes have been made you should review the changes and then commit them <code>svn commit -m "fixing formatting for release"</code> </li>
<li>Check release.properties and make sure that the scm properties have the right version. Sometimes the scm location can be the previous version not the next version.</li>
<li>Verify signatures (<a href="#verify_signatures">Verifying release signatures</a>)</li>
</ul>
</li>
<li>
-<p>Once any failures or required updates have been committed to svn, rollback the release prepare files:<br />
-</p>
-<div class="codehilite"><pre><span class="sb">`mvn -P apache-release release:rollback`</span>
+<p>Once any failures or required updates have been committed to svn, rollback the release prepare files: </p>
+<div class="codehilite"><pre>`<span class="n">mvn</span> <span class="o">-</span><span class="n">P</span> <span class="n">apache</span><span class="o">-</span><span class="n">release</span> <span class="n">release</span><span class="p">:</span><span class="n">rollback</span>`
</pre></div>
</li>
<li>
<p>Prepare the release: Run the "release:prepare" step for real this time. You'll be prompted for the same version information.</p>
-<div class="codehilite"><pre><span class="sb">`mvn -P apache-release release:prepare -DautoVersionSubmodules=true`</span>
+<div class="codehilite"><pre>`<span class="n">mvn</span> <span class="o">-</span><span class="n">P</span> <span class="n">apache</span><span class="o">-</span><span class="n">release</span> <span class="n">release</span><span class="p">:</span><span class="n">prepare</span> <span class="o">-</span><span class="n">DautoVersionSubmodules</span><span class="p">=</span><span class="n">true</span>`
</pre></div>
@@ -259,7 +256,7 @@ The popular software used Open Pretty Go
<ul>
<li>
<p>This step will create a maven staging repository and site for use in testing and voting. </p>
-<div class="codehilite"><pre><span class="sb">`mvn release:perform -Papache-release`</span>
+<div class="codehilite"><pre>`<span class="n">mvn</span> <span class="n">release</span><span class="p">:</span><span class="n">perform</span> <span class="o">-</span><span class="n">Papache</span><span class="o">-</span><span class="n">release</span>`
</pre></div>
@@ -276,8 +273,7 @@ The popular software used Open Pretty Go
<p>Verify the HTML links in site are correct</p>
</li>
<li>
-<p>Verify the staged artifacts in the nexus repo <br />
-</p>
+<p>Verify the staged artifacts in the nexus repo </p>
<ul>
<li>https://repository.apache.org/index.html</li>
<li>Staging repositories (under Build Promotion) --> Name column --> org.apache.airavata</li>
@@ -312,7 +308,7 @@ The popular software used Open Pretty Go
<ul>
<li>
<p>Checkout Airavata development dist area:</p>
-<div class="codehilite"><pre><span class="sb">`svn co https://dist.apache.org/repos/dist/dev/airavata airavata-dev-dist`</span>
+<div class="codehilite"><pre>`<span class="n">svn</span> <span class="n">co</span> <span class="n">https</span><span class="p">:</span><span class="o">//</span><span class="n">dist</span><span class="p">.</span><span class="n">apache</span><span class="p">.</span><span class="n">org</span><span class="o">/</span><span class="n">repos</span><span class="o">/</span><span class="n">dist</span><span class="o">/</span><span class="n">dev</span><span class="o">/</span><span class="n">airavata</span> <span class="n">airavata</span><span class="o">-</span><span class="n">dev</span><span class="o">-</span><span class="n">dist</span>`
</pre></div>
@@ -352,8 +348,7 @@ The popular software used Open Pretty Go
<p>Finalizing a release</p>
<ol>
<li>
-<p>The artificats in the repository are not yet mirrored and available for maven to download. Promote the staged nexus artifacts, but releasing them. <br />
-</p>
+<p>The artificats in the repository are not yet mirrored and available for maven to download. Promote the staged nexus artifacts, but releasing them. </p>
<ul>
<li>https://repository.apache.org/index.html</li>
<li>Staging repositories (under Build Promotion) --> Name column --> org.apache.airavata</li>
@@ -361,8 +356,7 @@ The popular software used Open Pretty Go
</ul>
</li>
<li>
-<p>Checkin the source and binary artifcats into distribution svn which will be pulled by all mirrors within 24 hours. The dist/dev svn is not mirrored, but the dist/release is. <br />
-</p>
+<p>Checkin the source and binary artifcats into distribution svn which will be pulled by all mirrors within 24 hours. The dist/dev svn is not mirrored, but the dist/release is. </p>
<ul>
<li><code>svn copy https://dist.apache.org/repos/dist/dev/airavata/${project.version}/RC{number} https://dist.apache.org/repos/dist/release/airavata/${project.version} -m "Committing Airavata Source and Binary Release for ${project.name}-${project.version}</code></li>
</ul>
@@ -418,8 +412,7 @@ The popular software used Open Pretty Go
</li>
<li></li>
<li>
-<p>Delete the build artifacts on people & www <br />
-</p>
+<p>Delete the build artifacts on people & www </p>
<ul>
<li>$ rm -rfv /www/people.apache.org/builds/airavata/${project.version}</li>
</ul>