Author: chrish
Date: Tue Dec 8 13:29:27 2015
New Revision: 1718594
URL: http://svn.apache.org/viewvc?rev=1718594&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=1718594&r1=1718593&r2=1718594&view=diff
==============================================================================
--- olingo/site/trunk/content/contribute.mdtext (original)
+++ olingo/site/trunk/content/contribute.mdtext Tue Dec 8 13:29:27 2015
@@ -53,21 +53,23 @@ To clone the current master branch of th
If you found a bug, please provide a detailed explanation how the bug can be
reproduced.
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
[here](https://issues.oasis-open.org/browse/ODATA/)
- * 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.
+
+ - 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
[here](https://issues.oasis-open.org/browse/ODATA/)
+ - 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.
**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.
- * 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.
+
+ - 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.
The default priority is Minor.
