Changes between Version 1 and Version 2 of ticket/1358/review


Ignore:
Timestamp:
2015-12-14T09:33:40+01:00 (5 years ago)
Author:
cbricaud
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • ticket/1358/review

    v1 v2  
    44 
    55== For completion by the Sci/Tech/Code reviewer == 
    6 '''Reviewer:''' [ Enter your name here ] 
     6'''Reviewer:''' Clement Bricaud 
    77 
    88=== Ticket Details, Documentation and Code changes === 
    9 ||Do you understand the area of code being altered and the reasoning why it is being altered?||YES/NO|| 
    10 ||Do the proposed code changes correspond with the stated reason for the change?||YES/NO|| 
    11 ||Is the in-line documentation accurate and sufficient?||YES/NO|| 
    12 ||Do the code changes comply with NEMO coding standards?||YES/NO|| 
    13 ||Is the Ticket documented with sufficient detail for others to understand the impact of the change?||YES/NO|| 
    14 ||Does any corresponding external documentation require updating?||YES/NO|| 
    15 ||If yes, which docs and have the updates been drafted?||YES/NO|| 
    16 ||Are namelist changes required for this change?||YES/NO|| 
     9||Do you understand the area of code being altered and the reasoning why it is being altered?||YES|| 
     10||Do the proposed code changes correspond with the stated reason for the change?||YES|| 
     11||Is the in-line documentation accurate and sufficient?||YES|| 
     12||Do the code changes comply with NEMO coding standards?||YES|| 
     13||Is the Ticket documented with sufficient detail for others to understand the impact of the change?||YES|| 
     14||Does any corresponding external documentation require updating?||YES|| 
     15||If yes, which docs and have the updates been drafted?||NO|| 
     16||Are namelist changes required for this change?||NO|| 
    1717||If yes, have they been done?||YES/NO|| 
    18 ||Has a completed Ticket Summary template been appended to the ticket to aid code reviews||YES/NO|| 
    19 ||Does this summary correspond with your understanding of the full ticket?||YES/NO|| 
     18||Has a completed Ticket Summary template been appended to the ticket to aid code reviews||YES|| 
     19||Does this summary correspond with your understanding of the full ticket?||YES|| 
    2020 
    2121Ticket, Documentation and Code comments 
     
    2424 
    2525=== Testing === 
    26 ||Has the NVTK and other jobs been tested with this change?||YES/NO|| 
     26||Has the NVTK and other jobs been tested with this change?||no specific configuration for SAO || 
    2727||Have the required bit comparability tests been run?||YES/NO|| 
    2828||Can this change be shown to have a null impact? (if option not selected)||YES/NO|| 
    2929||If no, is reason for the change valid/understood?||YES/NO/NA|| 
    3030||If no, ensure that the ticket details the impact this change will have on model configurations .||YES/NO/NA|| 
    31 ||Is this change expected to preserve all diagnostics?||YES/NO|| 
     31||Is this change expected to preserve all diagnostics?||YES|| 
    3232||If no, is reason for the change valid/understood?||YES/NO/NA|| 
    33 ||Are there significant changes in run time/memory?||YES/NO|| 
     33||Are there significant changes in run time/memory?|| ??? || 
    3434 
    3535Testing Comments 
     
    3737Add specific testing comments here 
    3838 
     39Is there a reason to keep a link to dtadyn is SAO_SRC ? 
     40Does thes changes lead to rutime/memory changes ? 
     41 
     42 
    3943Add specific testing comments here 
    4044 
    4145=== Code Review === 
    42 ||Do the code changes comply with NEMO coding standards?||YES/NO|| 
    43 ||Are code changes consistent with the design of NEMO?||YES/NO|| 
    44 ||Is the code free of unwanted TABs?||YES/NO|| 
    45 ||Has the code been wholly (100%) produced by NEMO developers working on NEMO?||YES/NO|| 
     46||Do the code changes comply with NEMO coding standards?||YES|| 
     47||Are code changes consistent with the design of NEMO?||YES|| 
     48||Is the code free of unwanted TABs?||YES|| 
     49||Has the code been wholly (100%) produced by NEMO developers working on NEMO?||YES|| 
    4650||If no, ensure collaboration agreement has been added to the ticket keywords|||| 
    4751