aries-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r787455 - /websites/staging/aries/trunk/content/development/releasingaries.html
Date Thu, 24 Mar 2011 10:27:40 GMT
Author: buildbot
Date: Thu Mar 24 10:27:40 2011
New Revision: 787455

Log:
Staging update by buildbot

Modified:
    websites/staging/aries/trunk/content/development/releasingaries.html

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 10:27:40
2011
@@ -283,22 +283,20 @@ Based on this, use the <a href="versionp
 the release process it is necessary to copy the new bundles to the dist dir and update table
on the web pages.</p>
 <h2 id="releasing_a_distribution">Releasing a distribution</h2>
 <h2 id="releasing_the_samples">Releasing the samples.</h2>
+<h1 id="background_information_on_the_apache_release_process">Background information
on the Apache Release process</h1>
 <p>To create a release you will need to create the release artifacts and move
 then to various places (ultimately the Maven central repository). The Maven
 commands and general outline of the process looks like this:</p>
 <p><img alt="rel" src="AriesRelease.png" /></p>
-<p>The picture assumes that you are releasing from a branch rather than from
-trunk. The full maven commands are not shown - the intention is just to
+<p>The full maven commands are not shown - the intention is just to
 give an indication of which maven commands you will need to use to create
-assets in different places.</p>
-<p>Performing a release is described in detail <a href="http://apache.org/dev/publishing-maven-artifacts.html.html">here</a>
+release artifacts in different places.</p>
+<p>Performing a release is described in detail <a href="http://apache.org/dev/publishing-maven-artifacts.html">here</a>
 . This document It covers all the steps listed above so on these pages we
-will only add things which are specific to the Apache Aries release. Note:
-the document has not been release and this link will need to be updated
-when it has.</p>
+will only add things which are specific to the Apache Aries release. </p>
 <p>There are a few steps to the process:</p>
 <ol>
-<li>Discussion of the release and its content on the aries-dev mailing list.</li>
+<li>Discussion of the release and its content on the dev@aries mailing list.</li>
 <li>Creating and storing GPG keys</li>
 <li>Setting up your environment</li>
 <li>JIRA preparation</li>
@@ -311,16 +309,14 @@ release:perform)</li>
 <li>Promoting the release artifacts to the Apache release repository</li>
 <li>Making the release artifacts available from the Aries web pages</li>
 <li>What to do when people find problems with the release artifacts</li>
-<li>JIRA tasks</li>
 </ol>
-<p>The best current documentation for releases is <a href="http://apache.org/dev/publishing-maven-artifacts.html">here</a>
- - but this isn't released yet. It covers all the steps listed above so on
+<p>The best current documentation for releases is <a href="http://apache.org/dev/publishing-maven-artifacts.html">here</a>.
It covers all the steps listed above so on
 these pages we will only add things which are specific to the Apache Aries
 release.</p>
 <p><a name="ReleasingAries-Discussionofthereleaseandit'scontentontheAriesmailinglist"></a></p>
 <h3 id="discussion_of_the_release_and_its_content_on_the_aries_mailing_list">Discussion
of the release and its content on the Aries mailing list</h3>
-<p>Before starting off the release process it is essential to gain concensus
-on the aries-dev list that this is the right time for a release and to
+<p>Before starting off the release process it is essential to gain consensus
+on the dev@aries list that this is the right time for a release and to
 agree its content. Allow at least a week for this discussion. </p>
 <p><a name="ReleasingAries-CreatingandstoringGPGkeys"></a></p>
 <h3 id="creating_and_storing_gpg_keys">Creating and storing GPG keys</h3>
@@ -332,7 +328,8 @@ instructions in the file) and checkin</p
 <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>
-<p>The recommendation is to avoid this unless you absolutely have to. </p>
+<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>
 
 <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">branches</span><span
class="o">/</span><span class="mi">0</span><span class="o">.</span><span
class="n">X</span><span class="o">-</span><span class="n">RCx</span>
<span class="o">\</span>
@@ -347,8 +344,8 @@ instructions in the file) and checkin</p
 </pre></div>
 
 
-<p><em>IMPORTANT</em> If you are using a branch to release you <em>must</em>
edit the top
-level pom.xml for each module to change the SCM references to point to the
+<p><em>IMPORTANT</em> If you are using a branch to release you <strong>must</strong>
edit the 
+pom.xml for <strong>each</strong> bundle to change the SCM references to point
to the
 branch and not to trunk. For example:</p>
 <div class="codehilite"><pre><span class="nt">&lt;connection&gt;</span>scm:svn:http://svn.apache.org/repos/asf/aries/branches/0.2-RCx/parent<span
class="nt">&lt;/connection&gt;</span>
 
@@ -373,7 +370,9 @@ for example:</p>
 </pre></div>
 
 
-<p>In general, if no Java files have changed there is nothing to release (??? check
this).</p>
+<p>In general, if no Java files have changed only the micro version of the bundle will
need to be incremented on release. If Java 
+code has changed it is important to check the packageinfo files to see whether package versions
have changed. If so
+these might lead to the requirement to increment the major or minor versions the bundle.</p>
 <p><a name="ReleasingAries-Checkingreleaseartifacts"></a></p>
 <h3 id="checking_release_artifacts">Checking release artifacts</h3>
 <p>Delete everything under ...org/apache/aries in your local
@@ -407,6 +406,7 @@ file does need one. As an alternative yo
 <h3 id="creating_a_snapshot_release">Creating a snapshot release</h3>
 <p>This is important to do when releasing from trunk as other bundles may want
 to continue to depend on the -SNAPSHOT version while the release is voted through.</p>
+<p>mvn deploy (check exact format)</p>
 <h3 id="jira_preparation">JIRA preparation</h3>
 <ul>
 <li>After initial release discussion on the mailing list you should have a list of
JIRA issues that are required in the release. If not, the default assumption is 'everything
that has been fixed since the last release'.</li>
@@ -417,9 +417,8 @@ to continue to depend on the -SNAPSHOT v
 <h3 id="creating_the_release">Creating the release</h3>
 <p><a name="ReleasingAries-Creatingthereleaseartifactsinastagingrepository"></a></p>
 <h5 id="creating_the_release_artifacts_in_a_staging_repository">Creating the release
artifacts in a staging repository</h5>
-<p>Aries is released as a set of modules, not all the modules in Aries are
-part of the release. Some modules depend on other modules. The release is
-created by releasing each module separately and in a specific order. It is
+<p>The release is
+created by releasing each bundle separately and in a specific order. It is
 also desirable to maintain the same IP address for the entire process (the
 staging repository is associated with your IP address, changing it results
 in the creation of a second staging repository).</p>
@@ -430,14 +429,6 @@ the next few steps.</p>
 </pre></div>
 
 
-<p>Then, change directory to 'parent'. It is necessary to release parent first
-because everything else depends on it. Run the following commands:</p>
-<div class="codehilite"><pre><span class="n">mvn</span> <span
class="n">install</span> <span class="o">-</span><span class="n">Papache</span><span
class="o">-</span><span class="n">release</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="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>
-
-
 <p><em>Note</em> The prepare step will make some assumptions about the
version of the
 development stream that is left after the release has been made. When
 releasing from a branch it may not be a good idea to accept the default for



Mime
View raw message