svn commit: r897109 [3/3] - in /websites/staging/marmotta/trunk/content: ./ apidocs/packages dependencies.html development.html

[bu...@apache.org]

Modified: websites/staging/marmotta/trunk/content/development.html
==============================================================================
--- websites/staging/marmotta/trunk/content/development.html (original)
+++ websites/staging/marmotta/trunk/content/development.html Mon Feb 10 09:18:33 2014
@@ -600,7 +600,7 @@
 <p>Issues are closed once the project against which it has been reported has been released. Issues once closed cannot be opened again. Rather new issues should be created against the new release to have broken implementations fixed or extended.</p></div></div>
 <div class="section">
 <h2>Development Practices<a name="Development_Practices"></a></h2>
-<p>@@TODO@@</p></div>
+<p>So far we are not following strcik development practices, but for code style guides we heavily base it heavily on the <a class="externalLink" href="http://www.oracle.com/technetwork/java/codeconv-138413.html">Code Conventions for the Java Programming Language</a> published by Oracle.</p></div>
 <div class="section">
 <h2><a name="contributing" id="contributing"></a> Contributing<a name="Contributing"></a></h2>
 <p>When reporting a bug, requesting a feature or propose an improvement, it is a good thing to attach a patch to the issue. This may speed up issue processing and helps you being recognized as a good community member leading to closer involvement with Marmotta.</p>