Changes between Version 6 and Version 7 of Developers/Developing Code Changes


Ignore:
Timestamp:
2010-04-14T20:24:41+02:00 (11 years ago)
Author:
rblod
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Developers/Developing Code Changes

    v6 v7  
    1717Merging back with the trunk is not described here. 
    1818 
    19 === Plan Your Change === 
     19== Plan Your Change == 
    2020A 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. 
    2121 
    22 === Create a Ticket === 
     22== Create a Ticket == 
    2323When 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. 
    2424 
     
    2828 * The ticket should be assigned to the code developer at this stage. 
    2929 
    30 === Create a Branch === 
     30== Create a Branch == 
    3131A development (dev) branch should be created and development can progress on this branch in the normal manner. 
    3232 
     
    5151 * If adding new functionality, remember to test that your new code doesn't change results when it is switched off. 
    5252 
    53 === Document your Change === 
     53== Document your Change == 
    5454 * 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. 
    5555 
     
    5858 * A sample wiki template (NEMOTicketTemplate) is provided when creating the wikipage 
    5959 
    60 === Science/Tech/Code Review === 
     60== Science/Tech/Code Review == 
    6161Once your change is complete, you will need to get it reviewed for scientific or technical correctness. 
    6262