karaf-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jbono...@apache.org
Subject svn commit: r1551925 - /karaf/site/production/index/developers/release-guide.html
Date Wed, 18 Dec 2013 12:45:01 GMT
Author: jbonofre
Date: Wed Dec 18 12:45:00 2013
New Revision: 1551925

URL: http://svn.apache.org/r1551925
Log:
[scm-publish] Updating main website contents

Modified:
    karaf/site/production/index/developers/release-guide.html

Modified: karaf/site/production/index/developers/release-guide.html
URL: http://svn.apache.org/viewvc/karaf/site/production/index/developers/release-guide.html?rev=1551925&r1=1551924&r2=1551925&view=diff
==============================================================================
--- karaf/site/production/index/developers/release-guide.html (original)
+++ karaf/site/production/index/developers/release-guide.html Wed Dec 18 12:45:00 2013
@@ -84,7 +84,7 @@
               </td>
               <td height="100%" width="100%">
                 <div class="wiki-content">
-<h1 id="HowtocreateandannounceaKarafrelease.">How to create and announce a Karaf release.</h1><h3
id="Requiredtoolspracticesandresources">Required tools, practices and resources</h3><ul><li>Use
Maven 2.0.11 or greater.</li><li>JDK 1.5 if version &lt; 2.3.0, JDK 1.6 otherwise.</li><li>Install
<a href="http://www.princexml.com/">princexml</a> 7.1 for manual generation.</li><li>Each
and every release must be <a href="http://www.apache.org/dev/release-signing.html">SIGNED</a></li><li>Your
public key should also be cross-signed by other Apache committers (not required, but suggested)</li><li>Make
sure you have all Apache servers defined in your <a href="http://maven.apache.org/developers/committer-settings.html">settings.xml</a></li><li>Subversion
client 1.7.8 or above.</li></ul><h3 id="Versioning">Versioning</h3><p>Sample
versioning:</p><div class="table-wrap"><table class="confluenceTable"><tr><th
class="confluenceTh"> SNAPSHOT </th><th class="confluenceTh"> RELEASE</th></tr><tr><td
cl
 ass="confluenceTd">1.0.0-SNAPSHOT </td><td class="confluenceTd"> 1.0.0</td></tr><tr><td
class="confluenceTd">1.1.0-SNAPSHOT </td><td class="confluenceTd"> 1.1.0</td></tr><tr><td
class="confluenceTd">1.1.1-SNAPSHOT </td><td class="confluenceTd"> 1.1.1</td></tr><tr><td
class="confluenceTd">1.1.2-SNAPSHOT </td><td class="confluenceTd"> 1.1.2</td></tr><tr><td
class="confluenceTd">2.0.0-SHAPSHOT </td><td class="confluenceTd"> 2.0.0</td></tr></table></div><h3
id="Prepare">Prepare</h3><p>To prepare and perform a release you must be at
least at Apache Karaf Committer.</p><p>Your settings.xml should look like:</p><pre>
+<h1 id="HowtocreateandannounceaKarafrelease.">How to create and announce a Karaf release.</h1><h3
id="Requiredtoolspracticesandresources">Required tools, practices and resources</h3><ul><li>Use
Maven 3.0.4 or greater.</li><li>JDK 1.5 if version &lt; 2.3.0, JDK 1.7 otherwise.</li><li>Install
<a href="http://www.princexml.com/">princexml</a> 7.1 for manual generation.</li><li>Each
and every release must be <a href="http://www.apache.org/dev/release-signing.html">SIGNED</a></li><li>Your
public key should also be cross-signed by other Apache committers (not required, but suggested)</li><li>Make
sure you have all Apache servers defined in your <a href="http://maven.apache.org/developers/committer-settings.html">settings.xml</a></li><li>Git
client 1.8 or greater</li></ul><h3 id="Versioning">Versioning</h3><p>Sample
versioning:</p><div class="table-wrap"><table class="confluenceTable"><tr><th
class="confluenceTh"> SNAPSHOT </th><th class="confluenceTh"> RELEASE</th></tr><tr><td
class="conf
 luenceTd">1.0.0-SNAPSHOT </td><td class="confluenceTd"> 1.0.0</td></tr><tr><td
class="confluenceTd">1.1.0-SNAPSHOT </td><td class="confluenceTd"> 1.1.0</td></tr><tr><td
class="confluenceTd">1.1.1-SNAPSHOT </td><td class="confluenceTd"> 1.1.1</td></tr><tr><td
class="confluenceTd">1.1.2-SNAPSHOT </td><td class="confluenceTd"> 1.1.2</td></tr><tr><td
class="confluenceTd">2.0.0-SHAPSHOT </td><td class="confluenceTd"> 2.0.0</td></tr></table></div><h3
id="Prepare">Prepare</h3><p>To prepare and perform a release you must be at
least at Apache Karaf Committer.</p><p>Your settings.xml should look like:</p><pre>
 &lt;settings>
   ...
   &lt;profiles>
@@ -144,7 +144,7 @@ and will start a release about next week
 
 -The Karaf Team
 </pre><h3 id="StagingtheReleaseCandidate">Staging the Release Candidate</h3><ol><li>Grab
the latest source<pre>
-git clone https://svn.apache.org/repos/asf/karaf.git
+git clone https://git-wip-us.apache.org/repos/asf/karaf.git
 </pre></li><li>Prepare your POMs for release:<ol><li>make sure
there is no snapshots in the POMs to be released</li><li>make sure everything
builds fine</li><li>check that your POMs will not lose content when they are rewritten
during the release process:<pre>
 mvn release:prepare -Pmanual -DdryRun
 </pre><p>Please diff the original pom.xml with the one named pom.xml.tag to see
if the license or any other info has been removed. This has been known to happen if the starting
&lt;project> tag is not a single line. The only things that should be different between
these files are the &lt;version> and &lt;scm> elements. If there are any other
changes, you must fix the original pom.xml file and commit before proceeding with the release.</p></li><li>publish
a snapshot<pre>



Mime
View raw message