Changes between Version 6 and Version 7 of Developers/DevelopingCodeChanges

Timestamp:

2010-04-14T20:24:41+02:00 (14 years ago)

Author:

rblod

Comment:

--

Developers/DevelopingCodeChanges

@@ -17 +17 @@
 Merging back with the trunk is not described here.
 
-=== Plan Your Change ===
+== Plan Your Change ==
 A discussion at an early stage with the NEMO Systems team/code owners should help make sure your change is viable, desirable and as easy as possible.
 
-=== Create a Ticket ===
+== Create a Ticket ==
 When a code change is being planned a ticket should be created describing the purpose of the change. The other fields in the ticket (e.g. Priority, Milestone, Keywords etc) should also be set appropriately.
 
@@ -28 +28 @@
  * The ticket should be assigned to the code developer at this stage.
 
-=== Create a Branch ===
+== Create a Branch ==
 A development (dev) branch should be created and development can progress on this branch in the normal manner.
 
@@ -51 +51 @@
  * If adding new functionality, remember to test that your new code doesn't change results when it is switched off.
 
-=== Document your Change ===
+== Document your Change ==
  * Any change will need documenting. If the documentation is fairly short (i.e. a small change with strictly limited impact), then the ticket will be an appropriate place for this. If documentation is more extensive, then a Trac wiki page should be used.
 
@@ -58 +58 @@
  * A sample wiki template (NEMOTicketTemplate) is provided when creating the wikipage
 
-=== Science/Tech/Code Review ===
+== Science/Tech/Code Review ==
 Once your change is complete, you will need to get it reviewed for scientific or technical correctness.