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 35 and Version 36 of Developers/DevProcess


Ignore:
Timestamp:
2016-02-24T16:22:28+01:00 (8 years ago)
Author:
nicolasmartin
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Developers/DevProcess

    v35 v36  
    22[[PageOutline(2,,inline)]] 
    33 
    4 ---- 
    54== Abstract == 
    65This section should be completed before starting to develop the code, in order to find agreement on the method beforehand. 
     
    2625Once the PI has completed this section, he should send a mail to the previewer(s) asking them to preview the work within two weeks. 
    2726 
    28 ---- 
    2927== Preview == 
    3028Since 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 his request.[[BR]]For each question, an iterative process should take place between PI and previewer(s) in order to reach a "YES" answer for each of the following questions. 
     
    4543Once all "YES" have been reached, the PI can start the development into his development branch. 
    4644 
    47 ---- 
    4845== Tests == 
    4946Once the development is done, the PI should complete this section below and ask the reviewers to start their review in the lower section. 
     
    6865 
    6966}}} 
    70 ---- 
     67 
    7168== Review == 
    7269A successful review is needed to schedule the merge of this development into the future NEMO release during next Merge Party (usually in November).