Author: buildbot
Date: Tue Dec 8 13:29:39 2015
New Revision: 974968
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:29:39 2015
@@ -1 +1 @@
-1718593
+1718594
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:29:39
2015
@@ -124,21 +124,25 @@ h2:hover > .headerlink, h3:hover > .head
<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">¶</a></h3>
<p><strong>Reporting a bug</strong> <br />
If you found a bug, please provide a detailed explanation how the bug can be
reproduced.</p>
-<p>You should mention the following properties:
- * Version of the library e.g. Olingo V4 (4.0.0-beta-03)
- * 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>
- * Often bugs are related to the underlying metadata document. Please append
the related part of the metadata document to reproduce the bug.
- * Provide a code snipped to reproduce the bug.
- * If you receive an exception, provide the stack trace of the exception.
- * Append further information in which part of the library the bug occurs.
(only if available)
- * 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.</p>
+<p>You should mention the following properties:</p>
+<ul>
+<li>Version of the library e.g. Olingo V4 (4.0.0-beta-03)</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>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 />
-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.
- * Major - This bug should be resolved as soon as possible in the normal
course of development activity, before the software is released.
- * 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>
+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 (default) - 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>
+</ul>
<p>The default priority is Minor.</p>
<h3 id="develop-the-according-bugfix-feature">Develop the according bugfix /
feature<a class="headerlink" href="#develop-the-according-bugfix-feature"
title="Permanent link">¶</a></h3>
<p><strong>Providing code</strong> <br />
