svn commit: r817232 - in /websites/staging/stanbol/trunk/content: ./ stanbol/development/index.html

[bu...@apache.org]

Author: buildbot
Date: Fri May 11 13:58:31 2012
New Revision: 817232

Log:
Staging update by buildbot for stanbol

Modified:
    websites/staging/stanbol/trunk/content/   (props changed)
    websites/staging/stanbol/trunk/content/stanbol/development/index.html

Propchange: websites/staging/stanbol/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri May 11 13:58:31 2012
@@ -1 +1 @@
-1337145
+1337166

Modified: websites/staging/stanbol/trunk/content/stanbol/development/index.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/development/index.html (original)
+++ websites/staging/stanbol/trunk/content/stanbol/development/index.html Fri May 11 13:58:31 2012
@@ -73,8 +73,7 @@ Apache Stanbol source code and contribut
 </ul>
 <p><a name="dependency-management"></a></p>
 <h2 id="dependency-management">Dependency Management</h2>
-<p>Apache Stanbol is a modular software stack and therefore all of its modules
-basically have different release cycles. Technically, this modularization
+<p>Apache Stanbol is a modular software stack. Technically, this modularization
 is implemented by the underlying OSGi component infrastructure. Each Apache
 Stanbol component is implemented as an OSGi bundle that can be deployed in
 an OSGi environment. Apache Stanbol uses the OSGi implementation from
@@ -148,8 +147,8 @@ are in place, the launchers are composed
 all required internal and external dependencies that have to be included in a
 launcher in order to make this component work. The dependencies are
 configured in a 'src/main/bundles/list.xml' file of each partial bundlelist
-artifact. The dependencies listed such a file for a partial bundlelist
-are more or less the same as the one defined for the build dependencies in
+artifact. The dependencies listed in such a file of a partial bundlelist
+are more or less the same as the ones defined for the build dependencies in
 the POM. But remember that the partial bundlelists define the dependencies
 needed at runtime and there may be other/more dependencies needed at runtime
 than at build time.</p>
@@ -197,6 +196,41 @@ developer has to keep in mind when writi
 </ul>
 <p><a name="release-management"></a></p>
 <h2 id="release-process">Release Process</h2>
+<p>Before you do any release related action, you should definitely read the
+<a href="http://www.apache.org/dev/#releases">release sections</a> on the Apache
+website and the
+<a href="http://incubator.apache.org/guides/releasemanagement.html">incubator release management pages</a>.</p>
+<p>The Apache Stanbol release management process is very similar to the one
+followed by the <a href="http://sling.apache.org/">Apache Sling</a> project. Their
+<a href="http://sling.apache.org/site/release-management.html">release management documentation</a>
+is a must read for Apache Stanbol committers. </p>
+<p>Apache Stanbol is a modular software stack and therefore all of its modules
+basically have different release cycles. So each component of Apache Stanbol
+may be released independently of others. The only requirement is, that a
+released Apache Stanbol component may not have any SNAPSHOT dependencies to
+any other component it depends on.</p>
+<p>To release a single component Apache Stanbol makes use the
+<a href="http://maven.apache.org/plugins/maven-release-plugin/">Maven Release plugin</a>.
+This plugin takes care of checking that there are no SNAPSHOT
+dependencies left. Additionally, there are some checks for legal issues
+automatically performed using the
+<a href="http://incubator.apache.org/rat/">Apache RAT</a> Maven plugin.</p>
+<p>To do a release test build, you have to activate the 'apache-release'
+profile, like it is done in this command:</p>
+<div class="codehilite"><pre><span class="nv">$</span> <span class="nv">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>
+</pre></div>
+
+
+<p>The 'apache-release' profile will be automatically activated when the Maven Release plugin is used. For staging an official release with signing the
+released artifact, making SVN tags, and uploading the artifact to the
+staging repository, you start with</p>
+<div class="codehilite"><pre><span class="nv">$</span> <span class="nv">mvn</span> <span class="n">release:prepare</span>
+</pre></div>
+
+
+<p>For further information we refer to the
+<a href="http://sling.apache.org/site/release-management.html">Apache Sling</a>
+website and their very good documentation of doing a release.</p>
   </div>
   
   <div id="footer">