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 45 and Version 46 of WikiStart


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

--

Legend:

Unmodified
Added
Removed
Modified
  • WikiStart

    v45 v46  
    1414= How to use this site =  
    1515 
    16 ''code browser : ''  
     16'''''code browser : '''''  
    1717The Trac browser can be used to browse directories, change logs and specific revisions of files stored in a subversion repository. 
    1818Directory 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. 
     
    2424https://forge.ipsl.jussieu.fr/nemo/browser/tags/nemo_v2_3 
    2525 
    26 ''new ticket : '' a ticket corresponds to a bug report. '''Please take care to fill the username field with a valid email'''. 
    27 A ticket contains the following information attributes: 
     26'''''new ticket : '''''  
     27Corresponds to a bug report. '''Please take care to fill the username field with a valid email'''.[[BR]] 
     28 
     29A ticket contains the following information attributes:[[BR]] 
    2830 
    2931Reporter - The author of the ticket.[[BR]] 
    30 Summary - A brief description summarizing the problem or issue. 
    31 Description - The body of the ticket. A good description should be specific, descriptive and to the point. 
    32 Component - The project module or subsystem this ticket concerns. 
    33 Version - Version of the project that this ticket pertains to. 
    34 Severity - What are the effects the issue described? Ranges from an enhancement request to blocker (must be fixed before next milestone). 
    35 Priority - The importance of is the issue relative to other tasks. 
    36 Keywords - Keywords that a ticket is marked with. Useful for searching and report generation. 
    37 Assigned to - Principal person responsible for handling the issue (here the NEMO team) 
    38 Cc - A list of other associated people. Note: this does not imply responsibility or any other policy. 
     32Summary - A brief description summarizing the problem or issue.[[BR]] 
     33Description - The body of the ticket. A good description should be specific, descriptive and to the point.[[BR]] 
     34Component - The project module or subsystem this ticket concerns.[[BR]] 
     35Version - Version of the project that this ticket pertains to.[[BR]] 
     36Severity - What are the effects the issue described? Ranges from an enhancement request to blocker (must be fixed before next milestone).[[BR]] 
     37Priority - The importance of is the issue relative to other tasks.[[BR]] 
     38Keywords - Keywords that a ticket is marked with. Useful for searching and report generation.[[BR]] 
     39Assigned to - Principal person responsible for handling the issue (here the NEMO team)[[BR]] 
     40Cc - A list of other associated people. Note: this does not imply responsibility or any other policy.[[BR]] 
    3941 
    40 view tickets : corresponds to all tickets submitted, active tickets corresponds to not yet solved. 
     42'''''view tickets :'''''[[BR]] 
     43 corresponds to all tickets submitted, active tickets corresponds to not yet solved. 
    4144 
    42 timeline : a sum up of what has been done on the svn repository 
     45'''''timeline :''''' a sum up of what has been done on the svn repository 
    4346 
    44 roadmap : brief description of current developments 
     47''''''roadmap :'''''' brief description of current developments 
    4548 
    4649= F.A.Q =