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

[bu...@apache.org]

Author: buildbot
Date: Fri Sep 27 15:06:36 2013
New Revision: 880116

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 Fri Sep 27 15:06:36 2013
@@ -1 +1 @@
-1526916
+1526938

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 Fri Sep 27 15:06:36 2013
@@ -71,7 +71,12 @@
             
             <h1 id="apache-olingo-release-documentation">Apache Olingo Release Documentation</h1>
 <h2 id="introduction">Introduction</h2>
-<p>This document describes the release guidelines for Apache Olingo.</p>
+<p>This document describes the release guidelines for Apache Olingo. It heavily refers 
+to <a href="http://maven.apache.org/developers/release/apache-release.html">standard Apache procedures to release</a>
+ Maven based projects at Apache.</p>
+<h2 id="build-environments">Build Environments</h2>
+<p>Apache Olingo is built and released with <a href="http://maven.apache.org">Maven3</a> and uses 
+the <a href="http://svn.apache.org/repos/asf/maven/pom/tags/apache-13/pom.xml">Apache POM version 13</a>.</p>
 <h2 id="release-artifacts">Release Artifacts</h2>
 <p>An Apache Olingo release consists of:</p>
 <ul>
@@ -110,6 +115,53 @@ processor and dependencies required to i
 files of the OData V2 reference scenarios implementations for the core library and the JPA processor. <br/> <strong>Package formats</strong>: zip.</p>
 </li>
 </ul>
+<h2 id="documentation-and-javadoc">Documentation and JavaDoc</h2>
+<p>The documentation that will be part of the release must match the code. 
+All examples in the documentation must work. The Java package documentation must be 
+up-to-date. Release independend documentation is maintained on the <a href="http://olingo.incubator.apache.org/documentation.html">Apache Olingo Documentation</a> page.</p>
+<h2 id="preparation">Preparation</h2>
+<h3 id="release-manager">Release Manager</h3>
+<p>A release manager must be appointed for a release. He or she is in charge of the release process, 
+following the guidelines and eventually generating the release artifacts.
+The release manager might tailor the process for a specific release.</p>
+<h3 id="version">Version</h3>
+<p>The OpenCMIS community decides if the release will be a major or a minor release and 
+agrees on a version number.</p>
+<h3 id="open-issues">Open Issues</h3>
+<p>There must not be any open JIRA issues for this release. There might be open issues for 
+future releases. Check with: <a href="https://issues.apache.org/jira/browse/OLINGO/fixforversion/12324804">fix for version view</a></p>
+<h3 id="unit-tests-and-integration-tests">Unit Tests and Integration Tests</h3>
+<p>All unit tests and integration tests must succeed on a 
+clean machine (starting with an empty local Maven repository). The following Maven 
+execution will run all unit and integration tests:</p>
+<div class="codehilite"><pre><span class="n">mvn</span> <span class="n">clean</span> <span class="n">install</span>
+</pre></div>
+
+
+<h3 id="apache-license-and-code-style">Apache License and Code Style</h3>
+<p>Each source code file must have a current ASF license header. The source 
+code should follow the Apache Olingo code style. For verification run following
+Maven execution</p>
+<div class="codehilite"><pre><span class="n">mvn</span> <span class="n">clean</span> <span class="n">install</span> <span class="o">-</span><span class="n">Pbuild</span><span class="p">.</span><span class="n">quality</span>
+</pre></div>
+
+
+<p>ackaging</p>
+<p>NOTICE, LICENSE and DISCLAIMER must be present in all bundles and must be up-to-date. </p>
+<p>Remote resources are provided by the ASF and the Maven <code>remote-resources-plugin</code> is 
+configured in the parent pom of the project.</p>
+<div class="codehilite"><pre><span class="nt">&lt;resourceBundle&gt;</span>org.apache:apache-jar-resource-bundle:1.4<span class="nt">&lt;/resourceBundle&gt;</span>
+<span class="nt">&lt;resourceBundle&gt;</span>org.apache:apache-incubator-disclaimer-resource-bundle:1.1<span class="nt">&lt;/resourceBundle&gt;</span>
+</pre></div>
+
+
+<h2 id="additional-apache-release-information">Additional Apache Release Information</h2>
+<ul>
+<li><a href="http://www.apache.org/dev/release.html">Releases Policy</a></li>
+<li><a href="http://www.apache.org/dev/release-publishing.html">Publishing Releases</a></li>
+<li><a href="http://www.apache.org/dev/publishing-maven-artifacts.html">Publishing Maven Artifacts</a></li>
+<li><a href="http://incubator.apache.org/guides/releasemanagement.html">Release Management During Incubation</a></li>
+</ul>