Author: buildbot
Date: Wed Dec 9 07:19:14 2015
New Revision: 975042
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 07:19:14 2015
@@ -1 +1 @@
-1718629
+1718767
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 07:19:14
2015
@@ -104,13 +104,16 @@ h2:hover > .headerlink, h3:hover > .head
<li><a href="#apache-olingo-how-to-contribute">Apache Olingo - How To
Contribute</a><ul>
<li><a href="#overview">Overview</a></li>
<li><a href="#contribute-via-git-patchpull-request-and-olingo-jira">Contribute
via Git-Patch/Pull-Request and Olingo-JIRA</a></li>
-<li><a href="#clone-the-olingo-project">Clone the Olingo Project</a></li>
<li><a href="#report-a-bug-or-feature">Report a bug or feature</a></li>
-<li><a href="#develop-the-according-bugfix-feature">Develop the according
bugfix / feature</a></li>
+<li><a href="#develop-the-according-bugfix-feature">Develop the according
bugfix / feature</a><ul>
+<li><a href="#clone-the-olingo-project">Clone the Olingo Project</a></li>
+<li><a href="#providing-bugfix-code">Providing bugfix / code</a></li>
<li><a href="#prepare-your-code-for-contribution">Prepare your code for
contribution</a></li>
</ul>
</li>
</ul>
+</li>
+</ul>
</div>
<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 chapter.</p>
@@ -123,20 +126,6 @@ h2:hover > .headerlink, h3:hover > .head
<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 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>
-<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>
-
-
-<p><strong>Olingo V4 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">odata4</span>
-</pre></div>
-
-
<h3 id="report-a-bug-or-feature">Report a bug or feature<a class="headerlink"
href="#report-a-bug-or-feature" title="Permanent link">¶</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>
@@ -160,12 +149,26 @@ The Olingo project uses the following de
</ul>
<p>The default priority is <strong>Minor</strong>.</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 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>
+<h4 id="clone-the-olingo-project">Clone the Olingo Project<a
class="headerlink" href="#clone-the-olingo-project" title="Permanent
link">¶</a></h4>
+<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>
+<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>
+
+
+<p><strong>Olingo V4 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">odata4</span>
+</pre></div>
+
+
+<h4 id="providing-bugfix-code">Providing bugfix / code<a class="headerlink"
href="#providing-bugfix-code" title="Permanent link">¶</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>
-<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>
+<h4 id="prepare-your-code-for-contribution">Prepare your code for
contribution<a class="headerlink" href="#prepare-your-code-for-contribution"
title="Permanent link">¶</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 />
You have done several commits and want to provide a single commit which
contains all your changes.</p>
