Changes between Version 4 and Version 5 of Developers/DevelopingCodeChanges

Timestamp:

2010-02-24T15:31:28+01:00 (14 years ago)

Author:

rblod

Comment:

--

Developers/DevelopingCodeChanges

@@ -1 +1 @@
 = '''Developing code change''' =
-
 Last edited [[Timestamp]]
 
@@ -16 +15 @@
  1. !'''Science/Tech/Code Review!'''. Review of the change by an expert on the scientific or technical area you are changing and for adherence to coding standards.
 
-
 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.
 
@@ -26 +24 @@
 
  * The !''milestone!'' field should be set to the area the change is being targeted for.
- * The ticket !''value!'' field should be set to "development branch"
+ * The ticket !''type!'' field should be set to "development branch"
  * Associated wiki page should be created by including the markup !wiki:ticket/xxxx (where xxxx is your ticket number) in your ticket and then following the link.
- * The ticket should be assigned to the code developer at this stage. 
+ * The ticket should be assigned to the code developer at this stage.
 
 === Create a Branch ===
@@ -46 +44 @@
 === Test your Change ===
 Test your change appropriately and record the results. The testing required will depend on the change and the potential impact on other configurations. When testing, things to consider include
- *  Testing on a variety of processor configurations (1xM, Nx1 and MxN are recommended)
+
+ * Testing on a variety of processor configurations (1xM, Nx1 and MxN are recommended)
 
  * Global and Limited-Area Models
  * Coupled Models?
  * If adding new functionality, remember to test that your new code doesn't change results when it is switched off.
- 
 
 === Document your Change ===
@@ -75 +73 @@
 
 Once the reviewer is satisfied, he/she should complete the approval section of the review template.
-