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.
2010WP/2010fromMergePartyToVersion3.3 (diff) – NEMO

Changes between Version 53 and Version 54 of 2010WP/2010fromMergePartyToVersion3.3


Ignore:
Timestamp:
2010-12-10T12:35:33+01:00 (14 years ago)
Author:
clevy
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • 2010WP/2010fromMergePartyToVersion3.3

    v53 v54  
    6565A number of commits have been done, and should have been fully tested. A standard general validation (i.e. with or identical to NVTK) should be done before tag: for each of the following reference configuration, test on: restartability (1 x 10 days / 5 days+ restart and 5days), reproducibility (MPP using 2 different domain decomposition give same results).[[BR]]List of reference configurations: ORCA2_LIM_PISCES, POMME, GYRE_LOBSTER, ORCA2_LIM_AGRIF , ORCA2_OFF_PISCES[[BR]]Once it is validated: 
    6666 
    67 '''Create nemo_v3_3_beta version in the trunk''' 
     67'''Build the new release (=nemo_v3_3_beta) version in the trunk''' 
    6868 
    6969This has to be checked carefully: we have both a lot of changes in the code, and a new organisation of the directories. The goal of the following proposition is to try to keep track of history of developments for as many routines as possible. 
    7070 
    71 1 - Move directories in the trunk to fit with 3_3_beta structure: 
     71'''1 - Move directories in the trunk to fit with 3_3_beta structure:''' 
    7272 
    7373Starting from the trunk, after the 3_2_2 tag: 
     
    8282Comments: this leaves NVTK and UTIL at the trunk level, is this what we want?) 
    8383 
    84 1 - Add the new release 3_3 in the trunk: 
     84'''2 - Add the new release 3_3 in the trunk:''' 
    8585 
    86 This has to be a direct copy: we do not want to do any merge at this stage: 
    87  
    88 Copy what we need of the 3_3_beta branch into the trunk: 
     86This has to be a direct copy: we do not want to do any merge at this stage. Copy what we need of the 3_3_beta branch into the trunk: 
    8987 
    9088{{{ 
     
    9694}}} 
    9795=== Tag and release of nemo_v3_3 === 
    98 Add the 3_3 tag: 
     96Create the 3_3 tag: 
    9997 
    100 Announce to users : mail to nemo@locean-ipsl.upmc.fr 
     98{{{ 
     99svn copy svn+ssh://yourloginforge@forge.ipsl.jussieu.fr/ipsl/forge/projets/nemo/svn/trunk  svn+ssh://yourloginforge@forge.ipsl.jussieu.fr/ipsl/forge/projets/nemo/svn/tags/nemo_v3_3 -m "Tagging nemo_v3_3" 
     100}}} 
     101Announce to users : mail to nemo users mailing list, based on informations below 
    101102 
    102103=== Delete the development branches for 2010 (if they went back to the new version of course) === 
     104Remains unclear for me: we definitely want to "stop these branches" which should not stay alive anymore. Do we really want to remove them?[[BR]]Yes because they are "dead" and we don't really want to deal with them anymore. No, because we will be loosing track of the different development stages for each branch. Still to be decided. If removal is decided, each developer hould do the work for his development branch. 
     105 
    103106---- 
    104107== Announcement of 3_3 to users  (To be improved, in particular by adding the ticket number to find more details of the development) ==