Author: buildbot
Date: Wed Feb  3 03:24:34 2016
New Revision: 979342

Log:
Staging update by buildbot for olingo

Modified:
    websites/staging/olingo/trunk/content/   (props changed)
    websites/staging/olingo/trunk/content/doc/odata2/release.html
    websites/staging/olingo/trunk/content/doc/odata4/release.html

Propchange: websites/staging/olingo/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Feb  3 03:24:34 2016
@@ -1 +1 @@
-1728252
+1728253

Modified: websites/staging/olingo/trunk/content/doc/odata2/release.html
==============================================================================
--- websites/staging/olingo/trunk/content/doc/odata2/release.html (original)
+++ websites/staging/olingo/trunk/content/doc/odata2/release.html Wed Feb  3 
03:24:34 2016
@@ -272,6 +272,15 @@ signatures) to <a href="http://www.apach
 <li>Release is closed in Jira.</li>
 <li>Release is announced to [email protected], [email protected].</li>
 </ul>
+<h3 id="maintain-release-distributions">Maintain Release Distributions<a 
class="headerlink" href="#maintain-release-distributions" title="Permanent 
link">&para;</a></h3>
+<p>To maintain the released Distributions for the download pages following 
steps are required (for more information see <a 
href="http://www.apache.org/dev/release-publishing.html#distribution_dist";>Apache
 Distribution Documentation</a>) to upload the new distribution via SVN 
(<code>svn co https://dist.apache.org/repos/dist/release/olingo</code>):</p>
+<ul>
+<li>Check out latest SVN revision via <code>svn co 
https://dist.apache.org/repos/dist/release/olingo</code></li>
+<li>Change into the directory according to the released Olingo artifact (e.g. 
<code>odata2</code>, <code>odata4</code>, ...)</li>
+<li>Create new directory according to release version (e.g 
<code>rel-x.x.x</code>) and copy all distribution artifacts (includes 
<em>.zip</em>, <em>.asc</em>, <em>.md5</em>, <em>.sha512</em>).</li>
+<li>Add new directory (e.g. <code>svn add rel-x.x.x</code>) and do the commit 
(e.g <code>svn ci -m "Added Olingo x.x.x release"</code>)</li>
+<li>Afterwards do a cleanup for the old releases according to the Apache 
Release Guidelines <a 
href="http://www.apache.org/dev/release.html#when-to-archive";>When</a> and <a 
href="http://www.apache.org/dev/release.html#how-to-archive";>How</a> to 
archive.</li>
+</ul>
 <h3 id="maintain-version-section-in-doap-file">Maintain Version Section in 
DOAP File<a class="headerlink" href="#maintain-version-section-in-doap-file" 
title="Permanent link">&para;</a></h3>
 <p><a 
href="http://olingo.apache.org/doap_Olingo.rdf";>http://olingo.apache.org/doap_Olingo.rdf</a></p>
 <p>Results are shown here:</p>

Modified: websites/staging/olingo/trunk/content/doc/odata4/release.html
==============================================================================
--- websites/staging/olingo/trunk/content/doc/odata4/release.html (original)
+++ websites/staging/olingo/trunk/content/doc/odata4/release.html Wed Feb  3 
03:24:34 2016
@@ -258,6 +258,15 @@ signatures) to <a href="http://www.apach
 <li>Release is closed in Jira.</li>
 <li>Release is announced to [email protected], [email protected].</li>
 </ul>
+<h3 id="maintain-release-distributions">Maintain Release Distributions<a 
class="headerlink" href="#maintain-release-distributions" title="Permanent 
link">&para;</a></h3>
+<p>To maintain the released Distributions for the download pages following 
steps are required (for more information see <a 
href="http://www.apache.org/dev/release-publishing.html#distribution_dist";>Apache
 Distribution Documentation</a>) to upload the new distribution via SVN 
(<code>svn co https://dist.apache.org/repos/dist/release/olingo</code>):</p>
+<ul>
+<li>Check out latest SVN revision via <code>svn co 
https://dist.apache.org/repos/dist/release/olingo</code></li>
+<li>Change into the directory according to the released Olingo artifact (e.g. 
<code>odata2</code>, <code>odata4</code>, ...)</li>
+<li>Create new directory according to release version (e.g 
<code>rel-x.x.x</code>) and copy all distribution artifacts (includes 
<em>.zip</em>, <em>.asc</em>, <em>.md5</em>, <em>.sha512</em>).</li>
+<li>Add new directory (e.g. <code>svn add rel-x.x.x</code>) and do the commit 
(e.g <code>svn ci -m "Added Olingo x.x.x release"</code>)</li>
+<li>Afterwards do a cleanup for the old releases according to the Apache 
Release Guidelines <a 
href="http://www.apache.org/dev/release.html#when-to-archive";>When</a> and <a 
href="http://www.apache.org/dev/release.html#how-to-archive";>How</a> to 
archive.</li>
+</ul>
 <h3 id="maintain-version-section-in-doap-file">Maintain Version Section in 
DOAP File<a class="headerlink" href="#maintain-version-section-in-doap-file" 
title="Permanent link">&para;</a></h3>
 <p><a 
href="http://olingo.apache.org/doap_Olingo.rdf";>http://olingo.apache.org/doap_Olingo.rdf</a></p>
 <p>Results are shown here:</p>


Reply via email to