Author: chrish
Date: Tue Dec 8 13:19:01 2015
New Revision: 1718588
URL: http://svn.apache.org/viewvc?rev=1718588&view=rev
Log:
CMS commit to olingo by chrish
Modified:
olingo/site/trunk/content/contribute.mdtext
Modified: olingo/site/trunk/content/contribute.mdtext
URL:
http://svn.apache.org/viewvc/olingo/site/trunk/content/contribute.mdtext?rev=1718588&r1=1718587&r2=1718588&view=diff
==============================================================================
--- olingo/site/trunk/content/contribute.mdtext (original)
+++ olingo/site/trunk/content/contribute.mdtext Tue Dec 8 13:19:01 2015
@@ -31,7 +31,7 @@ The Olingo uses the following process fo
4. Submit your JIRA ticket to receive feedback
-#### Clone the Olingo Project
+### Clone the Olingo Project
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.
To clone the current master branch of the Olingo project please use one of the
folling commands:
@@ -45,10 +45,10 @@ To clone the current master branch of th
git clone https://git-wip-us.apache.org/repos/asf/olingo-odata4
-#### Create an JIRA issue with your bug/feature request
+### Create an JIRA issue with your bug/feature request
-**Reporting a bug**
+**Reporting a bug**
If you found a bug, please provide a detailed explaination how the bug can be
reproduced.
You should meation the following properties:
@@ -60,7 +60,7 @@ You should meation the following propert
* 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.
-**Bug Priorities**
+**Bug Priorities**
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.
@@ -70,18 +70,18 @@ The Olingo project uses the following de
The default priority is Minor.
-#### Develop the according bugfix / feature
+### Develop the according bugfix / feature
-**Providing code**
+**Providing code**
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.
To append your contribution to a JIRA ticket, please create a patch file as
explained in the chapter.
-**Providing documentation for the Apache website**
+**Providing documentation for the Apache website**
To provide documentaion or tutorials you should write your contribution using
Markdown syntax.
-#### Prepare your code for contribution
+### Prepare your code for contribution
To append you contribution to a JIRA issue, please create a [patch
file](https://git-scm.com/docs/git-format-patch). The commit message should
contain the JIRA request number (e.g. OLINGO-42) and a short commit message.
