svn commit: r1032773 - /incubator/river/site/trunk/content/development-process.mdtext

[si...@apache.org]

Author: sijskes
Date: Mon Nov  8 22:33:52 2010
New Revision: 1032773

URL: http://svn.apache.org/viewvc?rev=1032773&view=rev
Log:
small fixes

Modified:
    incubator/river/site/trunk/content/development-process.mdtext

Modified: incubator/river/site/trunk/content/development-process.mdtext
URL: http://svn.apache.org/viewvc/incubator/river/site/trunk/content/development-process.mdtext?rev=1032773&r1=1032772&r2=1032773&view=diff
==============================================================================
--- incubator/river/site/trunk/content/development-process.mdtext (original)
+++ incubator/river/site/trunk/content/development-process.mdtext Mon Nov  8 22:33:52 2010
@@ -7,7 +7,9 @@ Title: Development Process
 
 * A JIRA issue is required for any substantive change.
 In order to keep the list of JIRA issues under control, it is expected that any controversial issue or user request for a feature or design change be discussed on the dev list prior to entering it into JIRA.
+
 * JIRA issues are not needed for small (e.g., typos) changes.
+
 * Issue discussions
 The preferred place of discussion on issues is the river-dev mail list. A link to the beginning of the mail thread on the issue should be placed in the JIRA issue so that users looking through JIRA can easily view the thread of discussion on an issue. Please keep the Subject line the same so that the email thread hangs together.  It's also recommended that a summary/conclusion on the thread be recorded in the JIRA issue itself.