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 23 and Version 24 of Developers/DevelopingCodeChanges


Ignore:
Timestamp:
2016-02-17T18:07:42+01:00 (8 years ago)
Author:
nicolasmartin
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Developers/DevelopingCodeChanges

    v23 v24  
    2828 
    2929== Detailed description of implementation plan and Preview step == 
    30 Once the workplan has been approved, the code development is planned. The PI should 
     30Once the workplan has been approved, the code development is planned. The PI should create: 
    3131 
    32  * create a !ticket to start the work. This !ticket will describe the purpose of the action, so as Pi and Previewer name. 
    33  * Create an associated wiki page using the [http://forge.ipsl.jussieu.fr/nemo/wiki/PageTemplates/NEMO_Devlt_Preview_and_ReviewTemplate development preview and review template]. This wiki page will permit to follow the ongoing work through different steps. The wiki page will be linked to the !ticket. 
     32 * A !ticket to start the work. This !ticket will describe the purpose of the action, so as Pi and Previewer name. 
     33 * An associated wiki page using the [http://forge.ipsl.jussieu.fr/nemo/wiki/PageTemplates/NEMO_Devlt_Preview_and_ReviewTemplate development preview and review template]. This page will permit to follow the ongoing work through different steps and will be linked to the !ticket. 
    3434 
    3535The other fields in the !ticket (e.g. Priority, Milestone, Keywords etc) should also be set appropriately. 
     
    3838 * The !ticket !''type!'' field should be set to "development branch" 
    3939 * Associated wiki page should be created by including the markup !wiki:ticket/xxxx (where xxxx is your !ticket number) in your !ticket and then following the link. 
    40  * The !ticket should be assigned to the code developer and the previewer at this stage. 
     40 * The !ticket should be assigned to the code developer, '''previewers and possible followers should be added in the 'cc' field for further email notification.''' 
    4141 
    4242The wiki page will describe: 
     
    5252 
    5353Once the wiki page is completed by PI (detailed implementation plan), the PI will submit it to Previewer. The Previewer will discuss with PI to reach full agreement on detailed implementation plan (in a maximum of 2 weeks starting when PI submits wiki page to Previewer).[[BR]]The PI is responsible to give all requested details.[[BR]]The Previewer is responsible to check with all experts that implementation plan is indeed coorect and compatible with the other developments going on in parallel during the year.  Objective is to avoid the need for a full rewriting at the end (which did happen sometimes previously) 
    54  
    5554== Start the coding == 
    5655Once the Previewer has sent the green light (approval of detailed implementation plan and summary of changes in reference manual), the PI can created the corresponding  development branch. The branch should be created from the up to date version of NEMO as chosen for each year (usually the trunk at a give fixed revision for a give year, see minutes of NEMO System Team videoconferences.  Development can progress on this new branch.