Changes between Version 45 and Version 46 of WikiStart
- Timestamp:
- 2008-01-17T16:37:16+01:00 (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
WikiStart
v45 v46 14 14 = How to use this site = 15 15 16 '' code browser :''16 '''''code browser : ''''' 17 17 The Trac browser can be used to browse directories, change logs and specific revisions of files stored in a subversion repository. 18 18 Directory 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. … … 24 24 https://forge.ipsl.jussieu.fr/nemo/browser/tags/nemo_v2_3 25 25 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 : ''''' 27 Corresponds to a bug report. '''Please take care to fill the username field with a valid email'''.[[BR]] 28 29 A ticket contains the following information attributes:[[BR]] 28 30 29 31 Reporter - 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. 32 Summary - A brief description summarizing the problem or issue.[[BR]] 33 Description - The body of the ticket. A good description should be specific, descriptive and to the point.[[BR]] 34 Component - The project module or subsystem this ticket concerns.[[BR]] 35 Version - Version of the project that this ticket pertains to.[[BR]] 36 Severity - What are the effects the issue described? Ranges from an enhancement request to blocker (must be fixed before next milestone).[[BR]] 37 Priority - The importance of is the issue relative to other tasks.[[BR]] 38 Keywords - Keywords that a ticket is marked with. Useful for searching and report generation.[[BR]] 39 Assigned to - Principal person responsible for handling the issue (here the NEMO team)[[BR]] 40 Cc - A list of other associated people. Note: this does not imply responsibility or any other policy.[[BR]] 39 41 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. 41 44 42 timeline :a sum up of what has been done on the svn repository45 '''''timeline :''''' a sum up of what has been done on the svn repository 43 46 44 roadmap :brief description of current developments47 ''''''roadmap :'''''' brief description of current developments 45 48 46 49 = F.A.Q =