From: kanschat <kanschat@0785d39b-7218-0410-832d-ea1e28bc413d>
Date: Sat, 8 Dec 2012 19:09:01 +0000 (+0000)
Subject: add a note
X-Git-Url: https://gitweb.dealii.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=ebf74079b742618bcfde5b82018f3c006a9608bc;p=dealii-svn.git

add a note


git-svn-id: https://svn.dealii.org/trunk@27781 0785d39b-7218-0410-832d-ea1e28bc413d
---

diff --git a/deal.II/doc/development/svn.html b/deal.II/doc/development/svn.html
index 1d6badadc3..4a5641878f 100644
--- a/deal.II/doc/development/svn.html
+++ b/deal.II/doc/development/svn.html
@@ -47,13 +47,21 @@
   <h2>Creating a development branch</h2>
 
   <p>
-    Significant new functionality can often not be developed all at once. In a
+    Significant changes in the library often cannot be developed all at once. In a
     case like this, one can create a development branch in the subversion
     repository into which one can check in all necessary changes and from which
     one can merge the final set of changes into the main development line once
     ready. The <tt>svn</tt> program can be used
     to keep your branch up-to-date with the trunk.
   </p>
+  
+  <p><b>Note: </b> Maintaining a branch over a long time can become
+  quite cumbersome, since you have to merge changes on the trunk on a
+  regular basis so that the branch does not deviate too
+  much. Therefore, when adding functionality, like a new class or a
+  new function in a class or namespace, it is advisable not to create
+  a new branch, but to mark in the documentation clearly that this is
+  experimental. Before checking in, verify that the library compiles.</p>
 
   <p>
     Creating a branch works through the following steps: