You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@olingo.apache.org by bu...@apache.org on 2013/09/30 16:07:15 UTC

svn commit: r880518 - in /websites/staging/olingo/trunk/content: ./ doc/release.html

Author: buildbot
Date: Mon Sep 30 14:07:15 2013
New Revision: 880518

Log:
Staging update by buildbot for olingo

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

Propchange: websites/staging/olingo/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Sep 30 14:07:15 2013
@@ -1 +1 @@
-1527534
+1527574

Modified: websites/staging/olingo/trunk/content/doc/release.html
==============================================================================
--- websites/staging/olingo/trunk/content/doc/release.html (original)
+++ websites/staging/olingo/trunk/content/doc/release.html Mon Sep 30 14:07:15 2013
@@ -200,12 +200,27 @@ and release candidate number will be inc
 <li>Maven artifacts will be staged on repository.apache.org. A new staging repo 
 is created per RC and will be communicated upon release.</li>
 <li>Distribution commodity packages are staged at 
-http:/people.apache.org/~<username>/olingo/<version></li>
+http:/people.apache.org/~<username>/olingo/<version> </li>
 </ul>
-<p>Once candidate artifacts are available, release manager kicks off the VOTE process.</p>
+<p>Once candidate artifacts are available, release manager kicks off the <a href="http://incubator.apache.org/guides/releasemanagement.html#best-practice-incubator-release-vote">VOTE process</a>.</p>
 <p>If the vote fails, the raised issues will be fixed, a new release candidate will be 
 built and the VOTE process will be restarted.</p>
 <p>If the release candidate gets approved, we can proceed to release publishing.</p>
+<h3 id="publishing-the-release">Publishing the Release</h3>
+<p>If the release candidate gets approved, we can proceed to release publishing:</p>
+<ul>
+<li>release candidate maven artifacts are promoted in the Apache Maven Repository and 
+made available at https://repository.apache.org/content/groups/public/org/apache/olingo/</li>
+<li>Maven artifacts are automatically synced to Maven Central at 
+http://repo1.maven.org/maven2/org/apache/olingo</li>
+<li>release candidate commodity packages are synced (together with their checksum and 
+signatures) to http://www.apache.org/dist/olingo</li>
+<li>project version at http://chemistry.apache.org/java/opencmis.html  is updated</li>
+<li>release tag is renamed to final version</li>
+<li>release branch is created</li>
+<li>Release is closed in Jira</li>
+<li>Release is announced to dev@chemistry.apache.org, announce@apache.org</li>
+</ul>
 <h3 id="additional-apache-release-information">Additional Apache Release Information</h3>
 <ul>
 <li><a href="http://www.apache.org/dev/release.html">Releases Policy</a></li>