Changes between Version 4 and Version 5 of Developers/Developing Code Changes


Ignore:
Timestamp:
2010-02-24T15:31:28+01:00 (11 years ago)
Author:
rblod
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Developers/Developing Code Changes

    v4 v5  
    11= '''Developing code change''' = 
    2  
    32Last edited [[Timestamp]] 
    43 
     
    1615 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. 
    1716 
    18  
    1917Merging back with the trunk is not described here. 
    2018 
    21 === Plan Your Change ===  
     19=== Plan Your Change === 
    2220A 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. 
    2321 
     
    2624 
    2725 * The !''milestone!'' field should be set to the area the change is being targeted for. 
    28  * The ticket !''value!'' field should be set to "development branch" 
     26 * The ticket !''type!'' field should be set to "development branch" 
    2927 * 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. 
    30  * The ticket should be assigned to the code developer at this stage.  
     28 * The ticket should be assigned to the code developer at this stage. 
    3129 
    3230=== Create a Branch === 
     
    4644=== Test your Change === 
    4745Test 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 
    48  *  Testing on a variety of processor configurations (1xM, Nx1 and MxN are recommended) 
     46 
     47 * Testing on a variety of processor configurations (1xM, Nx1 and MxN are recommended) 
    4948 
    5049 * Global and Limited-Area Models 
    5150 * Coupled Models? 
    5251 * If adding new functionality, remember to test that your new code doesn't change results when it is switched off. 
    53   
    5452 
    5553=== Document your Change === 
     
    7573 
    7674Once the reviewer is satisfied, he/she should complete the approval section of the review template. 
    77