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

[bu...@apache.org]

Author: buildbot
Date: Tue Dec  8 13:19:15 2015
New Revision: 974963

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 Tue Dec  8 13:19:15 2015
@@ -1 +1 @@
-1718587
+1718588

Modified: websites/staging/olingo/trunk/content/contribute.html
==============================================================================
--- websites/staging/olingo/trunk/content/contribute.html (original)
+++ websites/staging/olingo/trunk/content/contribute.html Tue Dec  8 13:19:15 2015
@@ -106,7 +106,7 @@ h2:hover > .headerlink, h3:hover > .head
 2. Develop the according bugfix / feature
 3. Prepare your code for contribtion
 4. Submit your JIRA ticket to receive feedback</p>
-<h4 id="clone-the-olingo-project">Clone the Olingo Project<a class="headerlink" href="#clone-the-olingo-project" title="Permanent link">&para;</a></h4>
+<h3 id="clone-the-olingo-project">Clone the Olingo Project<a class="headerlink" href="#clone-the-olingo-project" title="Permanent link">&para;</a></h3>
 <p>The current development version can be found in the Apache git repository. Please note that there are two different repositories, one for Version 2 and one for Version 4 of the OData protocol.</p>
 <p>To clone the current master branch of the Olingo project please use one of the folling commands:</p>
 <p><strong>OData V2 Code</strong></p>
@@ -119,8 +119,8 @@ h2:hover > .headerlink, h3:hover > .head
 </pre></div>
 
 
-<h4 id="create-an-jira-issue-with-your-bugfeature-request">Create an JIRA issue with your bug/feature request<a class="headerlink" href="#create-an-jira-issue-with-your-bugfeature-request" title="Permanent link">&para;</a></h4>
-<p><strong>Reporting a bug</strong>
+<h3 id="create-an-jira-issue-with-your-bugfeature-request">Create an JIRA issue with your bug/feature request<a class="headerlink" href="#create-an-jira-issue-with-your-bugfeature-request" title="Permanent link">&para;</a></h3>
+<p><strong>Reporting a bug</strong>  <br />
 If you found a bug, please provide a detailed explaination how the bug can be reproduced.</p>
 <p>You should meation the following properties:
    * Version of the libray e.g. Olingo V4 (4.0.0-beta-03)
@@ -130,7 +130,7 @@ If you found a bug, please provide a det
    * If you receive an exception, provide the stack trace of the exception.
    * Append further information in which part of the libray the bug occurs. (only if available)
    * If you have fixed a bug, you can append the solution to the request. Further information how to sent your solution are provided in the following chapters.</p>
-<p><strong>Bug Priorities</strong>
+<p><strong>Bug Priorities</strong>  <br />
 The Olingo project uses the following definition of priorities:
    * Blocker - The bug must be fixed before the next release
    * Critical - The bug should be resolved immediately and must be fixed before the next major release.
@@ -138,13 +138,13 @@ The Olingo project uses the following de
    * Minor (default) - This bug should be repaired after serious bugs have been fixed.
    * Trivial -It can be resolved in a future major system revision or not be resolved at all.</p>
 <p>The default priority is Minor.</p>
-<h4 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></h4>
-<p><strong>Providing code</strong>
+<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>
+<p><strong>Providing code</strong>  <br />
 To provide a bug fix, checkout the current master branch of the project and develop your solution. In Olingo we truly belive in tests, so your contribution should at least contain tests that show that your contribution works as expected and also tests that reproductes 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>
+<p><strong>Providing documentation for the Apache website</strong>  <br />
 To provide documentaion or tutorials you should write your contribution using Markdown syntax.</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>
+<h3 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></h3>
 <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>
 You have done serval commits and want to provide a single commit which contains all your changes.</p>