Version 67 (modified by roblod, 12 years ago) (diff)

ParentLinkage(=)?

NEMO TRAC wiki

    Error: Page DownloadNEMOpage does not exist
    Error: Page NVTKpage does not exist

Last edited Timestamp?


Welcome to NEMO Trac

  • What is Trac ?

It mainly serves as a bug report / evolution database for the NEMO source code. You can report any bug, or post any suggestion for further developments here. Standard documentation and model description can be found on the standard website : http://www.nemo-ocean.eu You can still have a look on bug reports

To report a any bug or improvment, please login first with your NEMO website account, then go to new ticket and use the pre-filled form.
If you don't have an account, please register on the NEMO website first. Your account information will then be transfered to this website in up to 30 minutes.

Please do not forget to fill the email or usename field when subimitting a ticket

Feel free to make comments or ask questions to the NEMO System Team: nemo_st@…

Trac is brought to you by Edgewall Software, providing professional Linux and software development services to clients worldwide. Visit http://www.edgewall.com/ for more information.

How to use this site

  • code browser :

The Trac browser can be used to browse directories, change logs and specific revisions of files stored in a subversion repository.
The 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.

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 : https://forge.ipsl.jussieu.fr/nemo/browser/tags/nemo_v3

  • new ticket : Corresponds to a bug report. Please take care to fill the username field with a valid email.

A ticket contains the following information attributes:
Reporter - The author of the ticket.
Summary - A brief description summarizing the problem or issue.
Description - The body of the ticket. A good description should be specific, descriptive and to the point.
Component - The project module or subsystem this ticket concerns.
Version - Version of the project that this ticket pertains to.
Severity - What are the effects the issue described? Ranges from an enhancement request to blocker (must be fixed before next milestone).
Priority - The importance of is the issue relative to other tasks.
Keywords - Keywords that a ticket is marked with. Useful for searching and report generation.
Assigned to - Principal person responsible for handling the issue (here the NEMO team)
Cc - A list of other associated people. Note: this does not imply responsibility or any other policy.

  • view tickets : corresponds to all tickets submitted, active tickets corresponds to not yet solved.
  • timeline : a sum up of what has been done on the svn repository
  • roadmap : brief description of current developments

F.A.Q

  • What is the difference between this site and NEMO main page ?

This part is mainly dedicated to the developers. If you just aim to use the system as it is, you will find more information (User guide etc) on NEMO web page.

  • What happened to my Flyspray reports ?

Don't worry, they will be reported in Trac by the NEMO team and corrected (hopefully).

  • Where is the previous browser ?

http://forge.ipsl.jussieu.fr/nemo/viewvc/?root=nemo-svn