svn commit: r975050 - in /websites/staging/olingo/trunk/content: ./ contribute.html

[bu...@apache.org]

Author: buildbot
Date: Wed Dec  9 09:23:58 2015
New Revision: 975050

Log:
Staging update by buildbot for olingo

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

Propchange: websites/staging/olingo/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Dec  9 09:23:58 2015
@@ -1 +1 @@
-1718767
+1718782

Modified: websites/staging/olingo/trunk/content/contribute.html
==============================================================================
--- websites/staging/olingo/trunk/content/contribute.html (original)
+++ websites/staging/olingo/trunk/content/contribute.html Wed Dec  9 09:23:58 2015
@@ -123,34 +123,44 @@ h2:hover > .headerlink, h3:hover > .head
 <li>Clone the Olingo Project</li>
 <li>Report a bug or feature</li>
 <li>Develop the according bugfix / feature</li>
-<li>Prepare your code for contribution </li>
+<li>Prepare your code for contribution</li>
 <li>Submit your JIRA ticket to receive feedback</li>
 </ol>
 <h3 id="report-a-bug-or-feature">Report a bug or feature<a class="headerlink" href="#report-a-bug-or-feature" title="Permanent link">&para;</a></h3>
 <p>If have you found a bug, please provide a detailed explanation how the bug can be reproduced.</p>
 <p>You should mention the following properties:</p>
 <ul>
-<li>Version of the library e.g. Olingo V4 (4.0.0)</li>
+<li>Version of the library e.g. <code>(Java) V4 4.0.0</code></li>
 <li>If a part of the implementation is not compliant to the OData protocol, please link the related part of the speciation or provide a link to the related JIRA issue of OData protocol. The official OASIS-OData JIRA can be found <a href="https://issues.oasis-open.org/browse/ODATA/">here</a></li>
 <li>Often bugs are related to the underlying metadata document. Please append the related part of the metadata document to reproduce the bug.</li>
 <li>Provide a code snipped to reproduce the bug.</li>
 <li>If you receive an exception, provide the stack trace of the exception.</li>
-<li>Append further information in which part of the library the bug occurs. (only if available)</li>
+<li>Append further information in which part of the library the bug occurs (if available).</li>
 <li>If you have fixed a bug, you can append the solution to the request. Further information how to append your solution to a ticket are provided in the following chapters.</li>
 </ul>
-<p><strong>Bug Priorities</strong>  <br />
+<p><strong>Bug/Feature Priorities</strong>
 The Olingo project uses the following definition of priorities:</p>
 <ul>
-<li>Blocker - The bug must be fixed before the next release</li>
-<li>Critical - The bug should be resolved immediately and must be fixed before the next major release.</li>
-<li>Major - This bug should be resolved as soon as possible in the normal course of development activity, before the software is released.</li>
-<li>Minor (<strong>default</strong>) - This bug should be repaired after serious bugs have been fixed.</li>
-<li>Trivial - It can be resolved in a future major system revision or not be resolved at all.</li>
+<li><em>Blocker</em> - This bug/feature must be fixed/implemented before the next release</li>
+<li><em>Critical</em> - This bug/feature should be resolved/implemented immediately and must be fixed/implemented before the next major release.</li>
+<li><em>Major</em> - This bug/feature should be resolved/implemented as soon as possible in the normal course of development activity, before the software is released.</li>
+<li><em>Minor</em> (<strong>default</strong>) - This bug/feature should be fixed/implemented after serious bugs have been fixed/implemented.</li>
+<li><em>Trivial</em> - This bug/feature can be resolved in a future major system revision or not be resolved/implemented at all.</li>
 </ul>
 <p>The default priority is <strong>Minor</strong>.</p>
+<p><strong>Bug/Feature Types</strong>
+The Olingo project uses the following <em>types</em> for an issue:</p>
+<ul>
+<li><em>Feature</em> - An issue that introduced a new feature (behaviour) to the Olingo library (this could be e.g. an additional not yet implemented part of the OData specification or convenience methods)</li>
+<li><em>Improvement</em> - An issue that improves an existing feature (behaviour) of the Olingo library (this could be e.g. a convenience method or internal improvements which does not change behavior)</li>
+<li><em>Bug</em> - An issue that describes an incorrect behaviour of the Olingo library in relation to the according OData specification.</li>
+<li><em>Test</em> - An issue that only improve or exentds tests for the  Olingo library.</li>
+<li><em>Task</em> - An issue that improve or exentds basic parts for the Olingo library without changing code (or logic). This could be e.g. improvements or changes necessary for the build infrastructure.</li>
+<li><em>Question</em> - An issue that only is a question related to the Olingo library.</li>
+</ul>
 <h3 id="develop-the-according-bugfix-feature">Develop the according bugfix / feature<a class="headerlink" href="#develop-the-according-bugfix-feature" title="Permanent link">&para;</a></h3>
 <h4 id="clone-the-olingo-project">Clone the Olingo Project<a class="headerlink" href="#clone-the-olingo-project" title="Permanent link">&para;</a></h4>
-<p>The current development version can be found in the Apache git repository. 
+<p>The current development version can be found in the Apache git repository.
 Please note Olingo provides two different libraries. One one hand Olingo V2 which implements the OData V2 specification and Olingo V4, which implements the OData V4 specification.</p>
 <p>To clone the current master branch of the Olingo project please use one of the following commands:</p>
 <p><strong>Olingo V2 Code</strong></p>
@@ -166,11 +176,11 @@ Please note Olingo provides two differen
 <h4 id="providing-bugfix-code">Providing bugfix / code<a class="headerlink" href="#providing-bugfix-code" title="Permanent link">&para;</a></h4>
 <p>To provide a bug fix, checkout the current master branch of the project and develop your solution. In Olingo we truly believe in tests, so your contribution should at least contain tests that show that your contribution works as expected and also tests that reproduces the previous reported bug. If you provide a new feature your tests should reach at least 80 percent test-coverage.</p>
 <p>To append your contribution to a JIRA ticket, please create a patch file as explained in the chapter.</p>
-<p><strong>Providing documentation for the Apache website</strong>  <br />
-To provide documentation or tutorials you should write your contribution using Markdown syntax.</p>
+<p><strong>Providing documentation for the Apache website</strong>
+To provide documentation or tutorials you should write your contribution using <a href="www.apache.org/dev/cmsref#markdown">a Markdown syntax</a>.</p>
 <h4 id="prepare-your-code-for-contribution">Prepare your code for contribution<a class="headerlink" href="#prepare-your-code-for-contribution" title="Permanent link">&para;</a></h4>
 <p>To append you contribution to a JIRA issue, please create a <a href="https://git-scm.com/docs/git-format-patch">patch file</a>. The commit message should contain the JIRA request number (e.g.  OLINGO-42) and a short commit message.</p>
-<p><strong>Example - Create a patch file</strong>  <br />
+<p><strong>Example - Create a patch file</strong>
 You have done several commits and want to provide a single commit which contains all your changes.</p>
 <div class="codehilite"><pre><span class="p">...</span>
 <span class="n">git</span> <span class="n">commit</span> <span class="o">-</span><span class="n">m</span> &quot;<span class="p">[</span><span class="n">OLINGO</span><span class="o">-</span>42<span class="p">]</span> <span class="n">Start</span> <span class="n">development</span> <span class="n">new</span> <span class="n">feature</span>&quot;
@@ -183,7 +193,7 @@ You have done several commits and want t
 
 
 <p>First rebase your local history to create a single commit. After that create a patch file using <code>git format-patch</code>. Now you can upload and append your created patch file to the JIRA issue.</p>
-<p><strong>Example - Appling a patch file</strong>  <br />
+<p><strong>Example - Appling a patch file</strong>
 You like to apply a patch file named "OLINGO_42.patch". Use the following commands:</p>
 <div class="codehilite"><pre><span class="n">git</span> <span class="n">am</span> <span class="o">--</span><span class="n">signoff</span> <span class="n">OLINGO_42</span><span class="p">.</span><span class="n">patch</span>
 </pre></div><div align="center">