Author: buildbot
Date: Wed Jun  6 10:20:25 2012
New Revision: 820449

Log:
Staging update by buildbot for stanbol

Added:
    
websites/staging/stanbol/trunk/content/stanbol/images/stanbol-logo/stanbol-icon-transparent-64x64.png
   (with props)
    
websites/staging/stanbol/trunk/content/stanbol/images/stanbol-logo/stanbol-icon.svg
   (with props)
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 Wed Jun  6 10:20:25 2012
@@ -1 +1 @@
-1345153
+1346810

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 Wed 
Jun  6 10:20:25 2012
@@ -238,7 +238,12 @@ profile, like it is done in this command
 <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>
+<div class="codehilite"><pre><span class="nv">$</span> <span 
class="nv">mvn</span> <span class="n">release:prepare</span> <span 
class="o">-</span><span class="n">DpreparationGoals</span><span 
class="o">=</span><span class="n">clean</span> <span class="n">install</span> 
<span class="o">-</span><span class="n">DscmCommentPrefix</span><span 
class="o">=</span><span class="n">STANBOL</span><span class="o">-</span><span 
class="n">XXX:</span>
+</pre></div>
+
+
+<p>Please, replace the XXX with the corresponding Jira issue number. After the 
release was prepared and tags created, the release has to be staged. This is 
done by executing the following command.</p>
+<div class="codehilite"><pre><span class="nv">$</span> <span 
class="nv">mvn</span> <span class="n">release:perform</span> <span 
class="o">-</span><span class="n">DreleaseProfiles</span><span 
class="o">=</span><span class="n">apache</span><span class="o">-</span><span 
class="n">release</span> <span class="o">-</span><span 
class="n">DscmCommentPrefix</span><span class="o">=</span><span 
class="n">STANBOL</span><span class="o">-</span><span class="n">XXX:</span>
 </pre></div>
 
 

Added: 
websites/staging/stanbol/trunk/content/stanbol/images/stanbol-logo/stanbol-icon-transparent-64x64.png
==============================================================================
Binary file - no diff available.

Propchange: 
websites/staging/stanbol/trunk/content/stanbol/images/stanbol-logo/stanbol-icon-transparent-64x64.png
------------------------------------------------------------------------------
    svn:mime-type = image/png

Added: 
websites/staging/stanbol/trunk/content/stanbol/images/stanbol-logo/stanbol-icon.svg
==============================================================================
Binary file - no diff available.

Propchange: 
websites/staging/stanbol/trunk/content/stanbol/images/stanbol-logo/stanbol-icon.svg
------------------------------------------------------------------------------
    svn:mime-type = image/svg+xml


Reply via email to