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

Timestamp:

Nov 14, 2018 7:27:13 PM (6 years ago)

Author:

kanani

Comment:

--

doc/tec/developerrules

@@ -3 +3 @@
 Only authorized users are allowed to commit changes to the repository.
 
-'''1. Make sure your code complies to the [attachment:PALM_coding_standard.docx PALM coding standard].''' Strict rules apply to formatting of the PALM FORTRAN code.  [[BR]] [[BR]]
+'''1. Make sure your code complies to the [wiki:doc/tec/developerrules/palmstandard PALM coding standard].''' Strict rules apply to formatting of the PALM FORTRAN code.  [[BR]] [[BR]]
 '''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]]
@@ -60 +60 @@
 
 = How to work with svn branches =
-Following [attachment:howto_svn_branches.pdf presentation] holds a step-by-step guide of how to create, checkout, modify, commit and merge code development within an svn branch.
+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.