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/DevelopingCodeChanges (diff) – NEMO

Changes between Version 35 and Version 36 of Developers/DevelopingCodeChanges


Ignore:
Timestamp:
2017-05-15T01:40:16+02:00 (7 years ago)
Author:
nicolasmartin
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Developers/DevelopingCodeChanges

    v35 v36  
    3030Once the workplan has been approved, the code development is planned. The PI should create: 
    3131 
    32  * An '''associated wiki page''' to be created. Please follow carefully the following indications: 
    33    * '''Create page in `wiki/${YEAR}WP/${WORKING_GROUP|INSTITUTE}-${ACTION_NUMBER}_${PI}` using this [wiki:PageTemplates/Devlt_Work_Form template],and '''activate the "side to side" button on top right of the page to faciltatethis first edit 
    34    * '''DO NOT switch to wyziwig mode '''(it blows up the fomat and automatic completion in the page) 
    35    * Once the page is created, you do not need to edit it to complete the requested fields: just complete the fields in the writable areas and click on "Submit" button to save your additions 
    36    * Editing the page is only needed if your want to add some fields in the page 
    37  
    38   you can customize ithe page while editing in the !TracForm  container. 
    39  
    40  * The wiki page will describe: 
    41  
    42  * Purpose, motivation and main tasks of the action 
    43  * PI(S) & (P)Reviewer(s) name(s) 
    44  * Detailed  implementation plan: scientific, technical and an expected summary  of changes for NEMO reference manual to be written later. 
    45  * Detailed list of specific tests, see below 
    46  * (P)Review status 
     32* 2 '''associated wiki pages''' to be created. Please follow carefully the following indications: 
     33  * For editing, activate the "side to side" button on top right of the page to facilitate this first edit and '''do not switch to 'wyziwig' view mode''' (it blows up the format and automatic completion in the page) 
     34  * '''Create summary page in `wiki/${YEAR}WP/${WORKING_GROUP|INSTITUTE}-${ACTION_NUMBER}_${PI}/Summary` using this [wiki:PageTemplates/WorkPlanAction/Summary template]''' 
     35  * '''Create review page in `wiki/${YEAR}WP/${WORKING_GROUP|INSTITUTE}-${ACTION_NUMBER}_${PI}` using this [wiki:PageTemplates/WorkPlanAction template]''' 
     36  * Once this last page is created, you do not need to edit it like a typical wiki page to complete the requested fields: just complete the fields in the writeable areas and click on "Submit" button at the end of the section to save your additions 
     37  * Editing the page is only needed if your want to add some fields in the page, you can customize the page while editing outside the !TracForm container 
     38    {{{ 
     39       Yes 
     40       {{{#!TracForm 
     41          No 
     42       }}} 
     43       Yes 
     44    }}} 
     45  * The wiki page will describe: 
     46    * Purpose, motivation and main tasks of the action 
     47    * PI(S) & (P)Reviewer(s) name(s) 
     48    * Detailed  implementation plan: scientific, technical and an expected summary  of changes for NEMO reference manual to be written later. 
     49    * Detailed list of specific tests, see below 
     50    * (P)Review status 
    4751 
    4852This page will permit to follow the ongoing work through different  steps and will go with: 
    49  
    50  * A '''linked !ticket''' to gather the group discussion. The following fields have to be set in a appropriate way: 
    51    * ''''Cc': (P)Reviewer(s) and possible follower(s) should be added for further email notification.''' 
    52    * 'Component': the area the change is being targeted for. 
    53    * 'Type': 'development branch' 
    54    * 'Owner': the code developer 
     53* A '''linked !ticket''' to gather the group discussion. The following fields have to be set in a appropriate way: 
     54  * ''''Cc': (P)Reviewer(s) and possible follower(s) should be added for further email notification.''' 
     55  * 'Component': the area the change is being targeted for. 
     56  * 'Type': 'development branch' 
     57  * 'Owner': the code developer 
    5558 
    5659The other fields in the !ticket (e.g. 'Priority', 'Milestone', 'Keywords') should also be set appropriately.