Documentation.

h2/src/docsrc/html/advanced.html

@@ -1454,6 +1454,9 @@ prior opening a database connection.
 <p>
 Since version 1.2.140 it is possible to let the old h2 classes (v 1.2.128) connect to the database. 
 The automatic upgrade .jar file must be present, and the URL must start with <code>jdbc:h2v1_1:</code>.
+If the database should automatically connect using the old version if a database with the old format exists
+(without upgrade), and use the new version otherwise, then append <code>;NO_UPGRADE=TRUE</code>
+to the database URL.
 </p>
 
 <h2 id="limits_limitations">Limits and Limitations</h2>

h2/src/docsrc/html/changelog.html

@@ -19,7 +19,6 @@ Change Log
 
 <h2>Next Version (unreleased)</h2>
 <ul><li>The database upgrade (to upgrade from H2 version 1.1.x) has been simplified.
-    The setting NO_UPGRADE is no longer supported, instead use the database URL jdbc:h2v1_1:
 </li><li>The feature to log all errors (system properties h2.logAllErrors and h2.logAllErrorsFile) has been removed.
 </li><li>When starting the H2 Console, the properties file can now be completely disabled.
 </li><li>Server.openBrowser no longer writes to System.out directly if opening the URL failed.

h2/src/docsrc/html/faq.html

@@ -47,6 +47,8 @@ Frequently Asked Questions
     Is the GCJ Version Stable? Faster?</a><br />
 <a href="#how_to_translate">
     How to Translate this Project?</a><br />
+<a href="#how_to_contribute">
+    How to Contribute to this Project?</a><br />
 
 <h3 id="support">I Have a Problem or Feature Request</h3>
 <p>
@@ -265,4 +267,19 @@ For more information, see
 <a href="build.html#translating">Build/Translating</a>.
 </p>
 
+<h3 id="how_to_contribute">How to Contribute to this Project?</h3>
+<p>
+There are various way to help develop an open source project like H2. The first step could be to 
+<a href="build.html#translating">translate</a> the error messages and the GUI to your native language.
+Then, you could 
+<a href="build.html#providing_patches">provide patches</a>.
+Please start with small patches. That could be adding a test case to improve the 
+<a href="build.html#automated">code coverage</a> (the target code coverage for this project is 90%, higher is better).
+You will have to <a href="build.html">develop, build and run the tests</a>.
+Once you are familiar with the code, you could implement missing features from the 
+<a href="roadmap.html">feature request list</a>.
+I suggest to start with very small features that are easy to implement.
+Keep in mind to provide test cases as well.
+</p>
+
 <!-- [close] { --></div></td></tr></table><!-- } --><!-- analytics --></body></html>