Changes between Version 90 and Version 91 of Developers/DevProcess

Timestamp:

2019-10-25T11:59:08+02:00 (5 years ago)

Author:

nemo

Comment:

--

Developers/DevProcess

@@ -7 +7 @@
 == Summary #summary
 
-The following sections should be completed by the PI of the development, before starting to develop the code, in order to find agreement on the method and the implementation beforehand.
-
-||=Action       || ''{ACTION_NAME} Subject''                             ||
-||=PI(S)        || ''Names''                                             ||
-||=Digest       || ''Brief description with motivations and main tasks'' ||
-||=Dependencies || ''If any''                                            ||
-||=Branch       || source:/NEMO/branches/{YEAR}/dev_r{REV}_{ACTION_NAME} ||
-||=Previewer(s) || ''Names''                                             ||
-||=Reviewer(s)  || ''Names''                                             ||
-||=Wiki         || wiki:{YEAR}WP/{ACTION_NAME}                           ||
+The following sections should be completed by the PI of the development, before starting to develop the code, 
+in order to find agreement on the method and the implementation beforehand.
 
 === Description
@@ -27 +19 @@
 Describe flow chart of the changes in the code. \\
 List the Fortran modules and subroutines to be created/edited/deleted. \\
-Detailed list of new variables to be defined (including namelists), give for each the chosen name and description wrt coding rules.
+Detailed list of new variables to be defined (including namelists), 
+give for each the chosen name and description wrt coding rules.
 
 === Documentation updates
 
-Using previous parts, define the main changes to be done in the NEMO literature (manuals, guide, web pages, ...).
+Using previous parts, define the main changes to be done in the NEMO literature 
+(manuals, guide, web pages, ...).
 
 ----
@@ -39 +33 @@
 == Preview #preview_
 
-Since the preview step must be completed before the PI starts the coding, the previewer(s) answers are expected to be completed within the two weeks after the PI has sent the request to the previewer(s). \\
+Since the preview step must be completed before the PI starts the coding, 
+the previewer(s) answers are expected to be completed within the two weeks after 
+the PI has sent the request to the previewer(s). \\
 Then an iterative process should take place between PI and previewer(s) in order to find a consensus
 
-__Possible bootlenecks__:
+__Possible bottlenecks__:
 - the methodology
 - the flowchart and list of routines to be changed
-- the new list of variables wrt coding rules
+- the new list of variables ''wrt'' coding rules
 - the summary of updates in literature
 
@@ -54 +50 @@
 == Tests #tests
 
-Once the development is done, the PI should complete the tests section below and after ask the reviewers to start their review.
+Once the development is done, the PI should complete the tests section below and 
+after ask the reviewers to start their review.
 
-This part should contain the detailed results of SETTE tests (restartability and reproducibility for each of the reference configuration) and detailed results of restartability and reproducibility when the option is activated on specified configurations used for this test
+This part should contain the detailed results of SETTE tests 
+(restartability and reproducibility for each of the reference configuration) and 
+detailed results of restartability and reproducibility when 
+the option is activated on specified configurations used for this test
 
 __Regular checks__:
 - Can this change be shown to produce expected impact (option activated)?                                               
 - Can this change be shown to have a null impact (option not activated)?
-- Results of the required bit comparability tests been run: are there no differences when activating the development?
+- Results of the required bit comparability tests been run: 
+  are there no differences when activating the development?
 - If some differences appear, is reason for the change valid/understood?                                                                      
 - If some differences appear, is the impact as expected on model configurations?                                                              
@@ -70 +71 @@
 == Review #review
 
-A successful review is needed to schedule the merge of this development into the future NEMO release during next Merge Party (usually in November).
+A successful review is needed to schedule the merge of this development into the future NEMO release during
+next Merge Party (usually in November).
 
 __Assessments__:
 - Is the proposed methodology now implemented?
 - Are the code changes in agreement with the flowchart defined at preview step?
-- Are the code changes in agreement with list of routines and variables as proposed at preview step? \\If, not, are the discrepancies acceptable?
+- Are the code changes in agreement with list of routines and variables as proposed at preview step? \\
+  If, not, are the discrepancies acceptable?
 - Is the in-line documentation accurate and sufficient?
 - Do the code changes comply with NEMO coding standards?
 - Is the development documented with sufficient details for others to understand the impact of the change?
-- Is the project literature (manual, guide, web, ...) now updated or completed following the proposed summary in preview section?
+- Is the project literature (manual, guide, web, ...) now updated or completed following 
+  the proposed summary in preview section?
 
 __Finding__: