New URL for NEMO forge!   http://forge.nemo-ocean.eu

Since March 2022 along with NEMO 4.2 release, the code development moved to a self-hosted GitLab.
This present forge is now archived and remained online for history.
Developers/DevProcess (diff) – NEMO

Changes between Version 7 and Version 8 of Developers/DevProcess


Ignore:
Timestamp:
2016-02-02T07:21:03+01:00 (8 years ago)
Author:
clevy
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Developers/DevProcess

    v7 v8  
    4444---- 
    4545== Section 3: Review to be completed by the reviewer(s) == 
    46 Once the development is done, the PI should complete the test section below and ask the reviewers to start their review, and add the date in the table above. A sucessful review is needed to schedule the merge of this development into the future NEMO release during next Merge Party (usually in November)/ 
     46Once the development is done, the PI should complete the tests section below and ask the reviewers to start their review, and add the date in the table above. A sucessful review is needed to schedule the merge of this development into the future NEMO release during next Merge Party (usually in November). 
    4747 
    48 ===  Code changes and documentation === 
     48=== Test section (to be completed be PI) === 
     49|| Question || Discussion || Answer || 
     50|| Can this change be shown to produce expected impact? (if option activated)? || || || 
     51|| Can this change be shown to have a null impact? (if option not activated) || || || 
     52|| Detailed results of restartability and reproducibility when the option is activated. Please indicate the configuration used for this test || || || 
     53|| Detailed results of SETTE tests (restartability and reproducibility for each of the reference configuration) || || || 
     54|| I || || YES/NO || 
     55|| If no, is reason for the change valid/understood? || || YES/NO/NA || 
     56|| If no, ensure that the ticket details the impact this change will have on model configurations . || || YES/NO/NA || 
     57|| Is this change expected to preserve all diagnostics? || || YES/NO || 
     58|| If no, is reason for the change valid/understood? || || YES/NO/NA || 
     59|| Are there significant changes in run time/memory? || || YES/NO || 
     60 
     61=== Code changes and documentation === 
    4962|| Question || Discussion || Answer || 
    5063|| Is the proposed methodology now implemented? || || ||