aries-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r787465 - /websites/staging/aries/trunk/content/development/releasingaries.html
Date Thu, 24 Mar 2011 15:10:47 GMT
Author: buildbot
Date: Thu Mar 24 15:10:47 2011
New Revision: 787465

Staging update by buildbot


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 Thu Mar 24 15:10:47
@@ -271,12 +271,14 @@ of all Aries modules and their most rece
 <h3 id="what_version_will_be_released">What version will be released?</h3>
 <p>For each bundle on the list check how its package versions have changed since the
last release.
 Based on this, use the <a href="versionpolicy">versioning policy</a> to determine
the version of the bundle that should be released.</p>
-<h3 id="releasing_bundles">Releasing bundles.</h3>
-<p>For each bundle:
-  * Deploy a SNAPSHOT to the maven snapshot repository (mvn deploy)
-  * Build each module and run RAT checks
-  * Create the release artifacts (mvn release:prepare)
-  * Upload release artifacts to a staging repository (mvn release:perform)</p>
+<h3 id="releasing_bundles">Releasing bundles</h3>
+<p>For each bundle:</p>
+<li>Deploy a SNAPSHOT to the maven snapshot repository (mvn deploy)</li>
+<li>Build each module and run RAT checks</li>
+<li>Create the release artifacts (mvn release:prepare)</li>
+<li>Upload release artifacts to a staging repository (mvn release:perform)</li>
 <h3 id="complete_the_process">Complete the process</h3>
 <p>Once the bundles are in the staging repository, start a vote on the release. After
72 hours close the vote. To complete
 the release process it is necessary to copy the new bundles to the dist dir and update table
on the web pages.</p>

View raw message