Laboratoire ICAR » Plateforme TXM

h2. Ticket categories definition

* Administration: portal administration interface and tools (Portal project)
* Commands: any command related issue (all projects)
* Conventions: algorithms and terminology conventions (all projects)
* Documentation: any documentation issue (manuals, wikis, web pages...) (SH: Javadoc?)
* Import: any import module issue
* Preferences: RCP preferences issues
* Setup: desktop RCP setup issues
* Stats: statistic models issues
** Stats / R: R related statistic models issues
* Toolbox: any issue related to the Toolbox project
* UI: User Interface issues in the RCP project (SH: and GWT project?)
** UI / Interaction: user interface behavior issues
** UI / Link / Command: user interface hypertextual command behavior issues

h2. SVN commit messages

Each entry of the message :
* is prefixed with *RCP:* or *TBX:* or *WEB:* or *DOC:* or *<plugin name>:*
* then insert the nature of the commit for example : "add", "fix" "adds", "fixes" ...
* and insert the details
* if you need more than one line to describe the entry, prefix the following lines with "#"

Example:
<pre>
TBX: add adds an awesome new functionnality
TBX: fix fixes the XXX import module
# the flow was not Groovy enough
# end of this entry
DOC: add adds documentation of the new functionnality
</pre>

For further information about commit syntax, you can go on this page

https://github.com/erlang/otp/wiki/Writing-good-commit-messages