svn commit: r1526937 - /incubator/olingo/site/trunk/content/doc/release.mdtext

[sk...@apache.org]

Author: sklevenz
Date: Fri Sep 27 15:06:32 2013
New Revision: 1526937

URL: http://svn.apache.org/r1526937
Log:
CMS commit to olingo by sklevenz

Modified:
    incubator/olingo/site/trunk/content/doc/release.mdtext

Modified: incubator/olingo/site/trunk/content/doc/release.mdtext
URL: http://svn.apache.org/viewvc/incubator/olingo/site/trunk/content/doc/release.mdtext?rev=1526937&r1=1526936&r2=1526937&view=diff
==============================================================================
--- incubator/olingo/site/trunk/content/doc/release.mdtext (original)
+++ incubator/olingo/site/trunk/content/doc/release.mdtext Fri Sep 27 15:06:32 2013
@@ -20,7 +20,14 @@ Notice:    Licensed to the Apache Softwa
 
 ## Introduction
 
-This document describes the release guidelines for Apache Olingo.
+This document describes the release guidelines for Apache Olingo. It heavily refers 
+to [standard Apache procedures to release](http://maven.apache.org/developers/release/apache-release.html)
+ Maven based projects at Apache.
+
+## Build Environments
+
+Apache Olingo is built and released with [Maven3](http://maven.apache.org) and uses 
+the <a href="http://svn.apache.org/repos/asf/maven/pom/tags/apache-13/pom.xml">Apache POM version 13</a>.
 
 ## Release Artifacts
 
@@ -55,3 +62,68 @@ processor and dependencies required to i
    *  `org.apache.olingo-olingo.odata2.dist-${version}-ref.${ext}` <br/> A bundle containing ready-to-depoly WAR 
 files of the OData V2 reference scenarios implementations for the core library and the JPA processor. <br/> **Package formats**: zip.
 
+## Documentation and JavaDoc
+
+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 [Apache Olingo Documentation][1] page.
+
+## Preparation
+
+### Release Manager
+
+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.
+
+### Version
+
+The OpenCMIS community decides if the release will be a major or a minor release and 
+agrees on a version number.
+
+### Open Issues
+
+There must not be any open JIRA issues for this release. There might be open issues for 
+future releases. Check with: [fix for version view][2]
+
+### Unit Tests and Integration Tests
+
+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:
+
+    mvn clean install
+
+### Apache License and Code Style
+
+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
+
+    mvn clean install -Pbuild.quality
+ 
+ackaging
+
+NOTICE, LICENSE and DISCLAIMER must be present in all bundles and must be up-to-date. 
+
+Remote resources are provided by the ASF and the Maven `remote-resources-plugin` is 
+configured in the parent pom of the project.
+
+    <resourceBundle>org.apache:apache-jar-resource-bundle:1.4</resourceBundle>
+    <resourceBundle>org.apache:apache-incubator-disclaimer-resource-bundle:1.1</resourceBundle>
+  
+
+## Additional Apache Release Information
+
+  - [Releases Policy][3]
+  - [Publishing Releases][4]
+  - [Publishing Maven Artifacts][5]
+  - [Release Management During Incubation][6]
+
+
+  [1]: http://olingo.incubator.apache.org/documentation.html
+  [2]: https://issues.apache.org/jira/browse/OLINGO/fixforversion/12324804
+  [3]: http://www.apache.org/dev/release.html
+  [4]: http://www.apache.org/dev/release-publishing.html
+  [5]: http://www.apache.org/dev/publishing-maven-artifacts.html
+  [6]: http://incubator.apache.org/guides/releasemanagement.html
\ No newline at end of file