Changes between Version 23 and Version 24 of doc/tec/developerrules

Timestamp:

Jan 8, 2019 12:17:52 PM (6 years ago)

Author:

kanani

Comment:

--

doc/tec/developerrules

@@ -6 +6 @@
 '''2. Change source code in your current working copy and document all changes in the respective file headers''' under "{{{Current revisions:}}}". Additionally, all changes might be documented in a local file (e.g. {{{~/palm/current_version/CURRENT_MODIFICATIONS}}}), including the names of those files that have been changed. Classify changes in three cases, new (N), changed (C), and bugfix (B). Try to be as short and as precise as possible in describing the changes! [[BR]] [[BR]]
 '''3. Test the changed version, until it works sufficiently.''' Starting with r2515 the script {{{palmtest}}} is available which can be used to test the current state of the trunk ([wiki:doc/tec/testsuite details] about palmtest). [[BR]] [[BR]]
-'''4. Run the script document_changes to save the change comments''' ('''NOT''' for [attachment:howto_svn_branches.pdf branches]). After having made your changes in the source code, simply call
+'''4. Run the script document_changes to save the change comments''' ('''NOT''' for [#branches branches]). After having made your changes in the source code, simply call
       {{{
          document_changes trunk
@@ -57 +57 @@
       The id tag in the modified source code will change accordingly.
 
-'''6. Enter the changes into the [wiki:/doc/tec/changelog change log]''' ('''NOT''' for [attachment:howto_svn_branches.pdf branches]). [[BR]] [[BR]]
+'''6. Enter the changes into the [wiki:/doc/tec/changelog change log]''' ('''NOT''' for [#branches branches]). [[BR]] [[BR]]
 
-= How to work with svn branches =
+= [=#branches How to work with svn branches] =
 Click [wiki:doc/tec/developerrules/svnbranch here] to find a step-by-step guide of how to create, checkout, modify, commit and merge code development within an svn branch.