Author: buildbot
Date: Tue Dec 8 13:27:41 2015
New Revision: 974966
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:27:41 2015
@@ -1 +1 @@
-1718588
+1718592
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:27:41
2015
@@ -99,16 +99,18 @@
h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
<h1 id="apache-olingo-how-to-contribute">Apache Olingo - How To Contribute<a
class="headerlink" href="#apache-olingo-how-to-contribute" title="Permanent
link">¶</a></h1>
<h3 id="overview">Overview<a class="headerlink" href="#overview"
title="Permanent link">¶</a></h3>
-<p>If you want to contribute to the Olingo Project, you can submit patches,
report bugs or provide documentation and tutorials. Contributions are managed
in the project <a href="https://issues.apache.org/jira/browse/OLINGO";>JIRA</a>.
So if you found a bug or want to provide a contribution please open a new <a
href="https://issues.apache.org/jira/browse/OLINGO";>JIRA</a> ticket. Detailed
information how to contribute can be found in the following capter.</p>
+<p>If you want to contribute to the Olingo Project, you can submit patches,
report bugs or provide documentation and tutorials. Contributions are managed
in the project <a href="https://issues.apache.org/jira/browse/OLINGO";>JIRA</a>.
So if you found a bug or want to provide a contribution please open a new <a
href="https://issues.apache.org/jira/browse/OLINGO";>JIRA</a> ticket. Detailed
information how to contribute can be found in the following chapter.</p>
<h3 id="contribute-via-git-patchpull-request-and-olingo-jira">Contribute via
Git-Patch/Pull-Request and Olingo-JIRA<a class="headerlink"
href="#contribute-via-git-patchpull-request-and-olingo-jira" title="Permanent
link">¶</a></h3>
-<p>The Olingo uses the following process for contributins:
-1. Reporting a bug or feature
-2. Develop the according bugfix / feature
-3. Prepare your code for contribtion
-4. Submit your JIRA ticket to receive feedback</p>
+<p>The Olingo uses the following process for contributions:</p>
+<ol>
+<li>Report a bug or feature</li>
+<li>Develop the according bugfix / feature</li>
+<li>Prepare your code for contribution </li>
+<li>Submit your JIRA ticket to receive feedback</li>
+</ol>
<h3 id="clone-the-olingo-project">Clone the Olingo Project<a
class="headerlink" href="#clone-the-olingo-project" title="Permanent
link">¶</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>To clone the current master branch of the Olingo project please use one of
the following commands:</p>
<p><strong>OData V2 Code</strong></p>
<div class="codehilite"><pre><span class="n">git</span> <span
class="n">clone</span> <span class="n">https</span><span
class="p">:</span><span class="o">//</span><span class="n">git</span><span
class="o">-</span><span class="n">wip</span><span class="o">-</span><span
class="n">us</span><span class="p">.</span><span class="n">apache</span><span
class="p">.</span><span class="n">org</span><span class="o">/</span><span
class="n">repos</span><span class="o">/</span><span class="n">asf</span><span
class="o">/</span><span class="n">olingo</span><span class="o">-</span><span
class="n">odata2</span>
</pre></div>
@@ -121,15 +123,15 @@ 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 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)
- * If a part of the implementation is not compliant to the OData protocol,
please link the the related part of the spefication or provide a link to the
related JIRA issue of OData protcoll. The offical OASIS-OData JIRA can be found
<a href="https://issues.oasis-open.org/browse/ODATA/";>here</a>
- * Often bugs are related to the underlaying metadata document. Please
append the related part of the metadata document to reproduce the bug.
- * Provide a code snipped to reproducte the bug.
+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 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>
+ * 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><strong>Bug Priorities</strong> <br />
The Olingo project uses the following definition of priorities:
* Blocker - The bug must be fixed before the next release
@@ -140,14 +142,14 @@ The Olingo project uses the following de
<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 />
-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>
+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 documentaion or tutorials you should write your contribution using
Markdown syntax.</p>
+To provide documentation or tutorials you should write your contribution using
Markdown syntax.</p>
<h3 id="prepare-your-code-for-contribution">Prepare your code for
contribution<a class="headerlink" href="#prepare-your-code-for-contribution"
title="Permanent link">¶</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>
+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> "<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>"
<span class="n">git</span> <span class="n">commit</span> <span
class="o">-</span><span class="n">m</span> "<span class="p">[</span><span
class="n">OLINGO</span><span class="o">-</span>42<span class="p">]</span> <span
class="n">Added</span> <span class="n">new</span> <span
class="n">tests</span>"
@@ -158,7 +160,7 @@ You have done serval commits and want to
</pre></div>
-<p>First rebase your local history to create a single commit. Afer that create
a patch file using git format-patch. Now you can upload and append your created
patch file to the JIRA issue.</p>
+<p>First rebase your local history to create a single commit. After that
create a patch file using git format-patch. Now you can upload and append your
created patch file to the JIRA issue.</p>
<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>
0001<span class="o">-</span><span class="n">Test</span><span
class="p">.</span><span class="n">patch</span>
