From ebf74079b742618bcfde5b82018f3c006a9608bc Mon Sep 17 00:00:00 2001 From: kanschat Date: Sat, 8 Dec 2012 19:09:01 +0000 Subject: [PATCH] add a note git-svn-id: https://svn.dealii.org/trunk@27781 0785d39b-7218-0410-832d-ea1e28bc413d --- deal.II/doc/development/svn.html | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) 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 @@

Creating a development branch

- 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 svn program can be used to keep your branch up-to-date with the trunk.

+ +

Note: 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.

Creating a branch works through the following steps: -- 2.39.5