Changes between Version 5 and Version 6 of SvnRules

Timestamp:

10/23/14 09:47:01 (10 years ago)

Author:

dneise

Comment:

--

SvnRules

@@ -61 +61 @@
 
 It is actually common practice that not the most recent version of the trunk is used for production. Very often software developers create certain release versions of their code, which is used for production, while development continues in the trunk. Code releases are often marked by so called **tags** for easy reference, but so far FACT did not follow this practise.
-However you might find yourself in the situation, that you want to base your development on 
+However you might find yourself in the situation, that you want to base your development on a version, from a given date.
 
+So suppose you want to let your branch be based on Mars, as it was on e.g. 26.05.2014, you can use the trac timeline to find the according revision number. https://trac.fact-project.org/timeline
+
+In our example we learn, that the last change on that day was done in revision 17899, so we can type:
+
+    {{{
+    svn copy -r17899 https://trac.fact-project.org/svn/trunk/Mars https://trac.fact-project.org/svn/branches/MarsBranchBasedOn17899 -m "another idea, ..."
+    }}}
+
+After checking out this branch, you can check if you in fact did the right thing by changing into the working directory of your branch and do:
+
+    {{{
+    svn co <your branch>
+    cd <into that folder>
+    svn log -v -r0:HEAD --stop-on-copy --limit 1
+    }}}
+
+You'll get something like:
+
+    {{{
+    rxxx | Author | <A DATE> | 1 line
+    Changed paths:
+        A /project/branches/branch (from /project/trunk/folder:ryyy)
+    }}}
+    
+    The revision and path your branch were base on are: /project/trunk/folder:ryyy.
+    
 == Before you commit something ==