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.
WikiStart (diff) – NEMO

Changes between Version 42 and Version 43 of WikiStart


Ignore:
Timestamp:
2008-01-17T16:30:24+01:00 (16 years ago)
Author:
rblod
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WikiStart

    v42 v43  
    1414= How to use this site =  
    1515 
    16 code browser : since NEMO is now managed with SVN, the new code browser is only suitable for the SVN repository. Each release can be found under tags/TAGNAME. Last release is here : 
     16code browser :  
     17 
     18The Trac browser can be used to browse directories, change logs and specific revisions of files stored in a subversion repository. 
     19Directory entries are displayed in a list with sortable columns. The list entries can be sorted by name, size or date by clicking on the column headers. The sort order can be reversed by clicking on a given column header again. 
     20The browser can be used to navigate through the directory structure by clicking on the directory names. Clicking on filenames on the other hand will display the files change log. 
     21It's also possible to browse directories as they were in history, at any given repository revision. 
     22The default behavior is to display the latest revision but another revision number can easily be selected using the form at the top of the page. 
     23 
     24Since NEMO is now managed with SVN, the new code browser is only suitable for the SVN repository. Each release can be found under tags/TAGNAME. Last release is here : 
    1725https://forge.ipsl.jussieu.fr/nemo/browser/tags/nemo_v2_3 
    1826 
    1927new ticket : a ticket corresponds to a bug report. '''Please take care to fill the username field with a valid email'''. 
     28A ticket contains the following information attributes: 
     29 
     30Reporter - The author of the ticket. 
     31Summary - A brief description summarizing the problem or issue. 
     32Description - The body of the ticket. A good description should be specific, descriptive and to the point. 
     33Component - The project module or subsystem this ticket concerns. 
     34Version - Version of the project that this ticket pertains to. 
     35Severity - What are the effects the issue described? Ranges from an enhancement request to blocker (must be fixed before next milestone). 
     36Priority - The importance of is the issue relative to other tasks. 
     37Keywords - Keywords that a ticket is marked with. Useful for searching and report generation. 
     38Assigned to - Principal person responsible for handling the issue (here the NEMO team) 
     39Cc - A list of other associated people. Note: this does not imply responsibility or any other policy. 
    2040 
    2141view tickets : corresponds to all tickets submitted, active tickets corresponds to not yet solved.